what's your goal? (seperate backlog issues?)
one colum (your backlog) is mapped with an issue status which can not be used in another colum (would be quite confusing)
unless you add a new issue status i.e. "backlog2" you can't
maybe there is some other solution like using swimlanes...
please describe exactly what you're after...i'm pretty sure this can be managed
Thanks Faysal for the answer. What i am trying to achive is that there are two teams working on the same project what i want to do is to have two backlogs one for each team.. There wont be any duplicate issue between backlogs... i want to make two backlogs with different filters..
in this case i suggest using a customfield, components or labels.
you can insert value like "Team 1" or "Team 2" and run jql filtering on the board.
maybe this video explains more in detail (sorry its in german but just concentrate on what they're showing)
or simply refer to
it is more like several teams on one project. you're right. sorry
ok lets stick with swimlanes (if it is suitable for you) for the next example.
you could add 2 lanes..."Team 1" and "Team 2"
in the jql part you need to define on what you are planning to filter. at this point you'll need something like i already mentioned above..
if you think about components add 2 components (one for each team) to your project
add jql for swimlane "Team 1" to filter out the matching issues and do the same for "Team 2"
this will seperate applicable issues on one board seperated by swimlanes
one little bit bigger solution would look like this...
default backlog issues are in status "Open"
Team1 backlog issues are in status "Open:Team1"
Team2 backlog issues are in status "Open:Team2"
created issues will be "Open"
now add 2 transitions to your Workflow (Step 1)
you may want to add another transition to move the issue back to default backlog.
so if the issue is in status Open you can choose to which of the teams it should be send
also you can move it from Team1 to Team2 and vice versa
now the Rapidboard thing:
again we gonna use swimlanes:
did you get my point?
one more thing on the customfield part.
this could be a "select list" or "Radio Buttons" holding the values "Team1" , "Team2"
add it to the relevant screens and you can see it in Jiras issue-view
latest greenhopper is now able to show select list fields and radio buttons in "issue view details" too
you can try this solution (i just did it as well) -> WORKS
HI Faysal, Great solutions. I have another doubt here if you can help me to manage it in JIRA.
I have created workflow where there is status called "Validation" because I need Project Manager to validate the issue created. Before validation it should be visible in my scrum bord planning tab but not in product backlog (something similler to backlog). Once the issue is validated then it should go to the backlog.
let the issue which got created to be there in backlog without validation but i should not be able to assign it to any sprint without validation. when i try to do that it should ask me to validate it first.
Any solution for this.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs