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?
That's an easy way to do it, but you need to remember that a "backlog" belongs to a board.
So to do this, you'll need two boards. One with a filter that excludes your "tasks" and a second that includes them, and excludes the others.
I should create a new Board from the existing Project...correct? How do I create the filtering of the New Board, or re-filtering the Existing Board? I did a quick review of the Existing one but did not see any filter to edit. Please advise...thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, Sport, I need more detailed direction. I understand the concept you have provided; but, I do not understand how to implement it. Please advise...thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's what you need to edit. Once for each board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The order by clause has to come after the selection.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So project = CRM and issuetype = Task order by rank asc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you tried just "project = CRM and issuetype = Task order by rank asc"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Remove the other sort from it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes - it breaks ranking - you can't rank something if you're sorting by something else.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.