-
Suggestion
-
Resolution: Won't Fix
From documentation Assign statuses and edit columns in a team managed project/, it is indicated
For example, the done status category must be in the rightmost column for its issues to be cleared from your board. If you have multiple done states, like Won’t fix, Abandoned, and All done, you can assign them all to the rightmost column. Any issue moved to those three statuses will then be marked as resolved, and cleared from your board, if you use sprints.
This indicates how the last column will set the resolution of an issue, but considering that Team managed projects tend to be administered by people who may not be as familiar with Jira administration or the way boards work, it seems appropriate to provide additional messaging/tooltips to illustrate how the last column will affect issues, maybe an icon on the las column with an exclamation mark where you can see the message and/or link to the documentation would be helpful.
- relates to
-
JSWCLOUD-17670 Closing Sprints and use of the 'Done column'
- Closed
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!