I have one project & board, with multiple tickets in the backlog. We are not going to work on these tickets until late 2017. I don't want to delete them, since we'll need them in the future, but I also don't want to clutter my backlog with work that we don't need to discuss (or accidentally pull into a Sprint!).
The only possible action that I can think of to "hide" these in the backlog view, without deleting them, is to do a bulk move to a new project that I could call "Archived Project." Is there an easier solution to hide/archive within the current project that I could restore in the future?
Another project is one way to do it.
The other two options that spring to mind without coding are:
You could combine those ideas too, although it's a bit of a faff - have a security level that uses the custom field flag to hide things (then you don't need to alter filters)
Another way to achieve this is configure issue security level to Archived. And set issue security level for issues to Archive issues.
Then you set users with issue security level "Archived" only to access these issues. Once your time has come to re-leave it to public, then you can remove security level of these issues and it will e open for everyone. When you start working on issue securities you'll e most happiest person.
To create a new status, would I need to add it to the workflow? I suppose I could add it on the workflow, but not necessarily have anything move to or from it. I worry, though, that my users would "accidentally" move needed tickets to that status. I'll play around with it. Thanks!
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG