We want to differentiate Operations Tasks from Development issues (Bugs, Enhancements, etc.). If we enter these items, classified as Tasks, can JIRA collect them into a unique Backlog assortment?
Yes, that's the easiest way. All boards have a filter definition on the first configuration page - they get created for you when you create a board from a project. Follow the link in there to get to the filter display and you'll be able to edit and then save it. Your board will use it immediately.
I assume you know how to create a new board, so I won't try to parrot that. Go to the board you want to set up for backlog 1, click board -> configure, go to the "general and filter" tab if that's not the default one, click "edit filter" in the middle. When you land on the navigator, you may need to click "advanced" to get the JQL shown. Add "and issuetype = task" to it. Save the filter. Your board now only shows tasks. Repeat for board 2, but with a clause that says "and issuetype != task"
Perhaps a syntax issue...when entered as issuetype, the spell check within JIRA underlined it in red as it does here. Also, when I entered text the project marker changed from a green check mark to a white x with red background. Text entered was: project = CRM ORDER BY Rank ASC AND Issuetype = Task
That is the second Project...seems to work AOK. I am trying to modify the original Project to eliminate populating Tasks in both Projects. As I am not the Administrator of the original Project, I needed to wait until his availability to login and allow me to edit the filter. It appears to have saved correctly; but, now I can't order the issues sequentially because Ranking is disabled. Any suggestions?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot