Hello. I have just started using ServiceDesk Plus for project management in an agile environment. To me, being new at this, it seems like it would make more sense to have milestones be collections of requests instead of tasks because it seems like requests are more like product backlog items and milestones are what you might call themes or epics, and tasks would be, well, tasks, the discrete work that needs to be completed to complete the backlog request item.

 

I did find a way to associate the requests with projects and I think that will be useful. However, I have noticed that the tasks included in the requests do not show up in the count of tasks needed to complete the project. It seems like it would be useful to have an idea of all of the tasks that are open and associated with the project, not just the tasks associated with milestones that are associated with the project, which is what it seems to be now.

Also, it seems like it would be good to have a count of open requests like the count of open milestones and tasks that is already shown.

 

Could someone explain to me their approach in managing projects using tasks and milestones and how it makes sense to them? I am concerned that the tasks that would be attached to milestones would get lost in a sea of tasks associated with requests.