Enhancement Request - Project/Priority Management
Posted: 23 Jan 2019, 20:23
Hello!
Our team has been using Mantis for 5+ years now and we've altered our workflow over time to best accommodate our needs. However, we find that we're wasting too much time communicating the order of priority when it comes to bugs we're trying to get resolve for the current release cycle.
Below is some more detail:
1) Currently
a) Business Workflow: Our website release cycles are 3-4 weeks
b) Mantis Workflow: We create one (parent) bug, known as the Release Tracker. Then, we 'relate' all of the (children )bugs that need to be included in this Release, to the parent bug. This keeps all of the bugs in one, easy to view, place.
c) Drawback: When viewing the parent bug, we are not able to see the priority of each related (child) bug. Even if we could, this would not solve our need of communicating the real-time priority (top-to-bottom) of each bug. So, we are currently adding a comment every other business day listing the bugs in order of priority. It is time-consuming since new bugs are always opened, others are closed, and priorities change.
d) Enhancement Request: Add the ability to drag/move the child (related) bugs so that we can order them in the order of priority (i.e. top = highest priority and bottom = lowest priority). This way, our development team and we (the customer) can always manage and view the priorities of our enhancements in real-time.
Please let me know if you have any questions!
Thank you,
Michael Rothwell
Our team has been using Mantis for 5+ years now and we've altered our workflow over time to best accommodate our needs. However, we find that we're wasting too much time communicating the order of priority when it comes to bugs we're trying to get resolve for the current release cycle.
Below is some more detail:
1) Currently
a) Business Workflow: Our website release cycles are 3-4 weeks
b) Mantis Workflow: We create one (parent) bug, known as the Release Tracker. Then, we 'relate' all of the (children )bugs that need to be included in this Release, to the parent bug. This keeps all of the bugs in one, easy to view, place.
c) Drawback: When viewing the parent bug, we are not able to see the priority of each related (child) bug. Even if we could, this would not solve our need of communicating the real-time priority (top-to-bottom) of each bug. So, we are currently adding a comment every other business day listing the bugs in order of priority. It is time-consuming since new bugs are always opened, others are closed, and priorities change.
d) Enhancement Request: Add the ability to drag/move the child (related) bugs so that we can order them in the order of priority (i.e. top = highest priority and bottom = lowest priority). This way, our development team and we (the customer) can always manage and view the priorities of our enhancements in real-time.
Please let me know if you have any questions!
Thank you,
Michael Rothwell