How do you print cards when you have multiple projects with different components and versions?

In the Classic Baord with Card View, you can only group your cards by one project along with using components and versions. How do you gather your cards to print on a physical board if each of your projects have difference components and versions? How do you find your user stories related to the sprint you just planned?

3 answers

1 accepted

Accepted Answer
0 votes

I actually found a way to print my cards when using multiple projects. I created a label with the sprint number for all my applicable stories and tasks. I then created a issue filter that pulls those issues by that label. From the classic board, you can create a new project default. I named it "sprint x" and then in the filter section I selected my named Jira filter and perfecto! They all showed up for each of the 5 projects we use for my scrum board. My life just got easier when it comes time to print cards for the physical board.

Hi,

If you have planned sprint, that wouldn't be possible but if you have an active sprint, you can query all the user stories in the issue navigator, you can look at this article for the way to do this:

* https://confluence.atlassian.com/display/ONDEMANDKB/How+to+Get+the+Sprint+Filter+Link+in+the+Rapid+Board

Please let us know if you need any further help.

Cheers,

Omar

Thanks for the feedback, but there is still limitations on how the information is grouped for printing. I like the ability to customize the fields displayed on my cards.

May be you should Go Green. Use a large TV and stop printing cards :)

If that would only be an option for me. We are still in the agile transformation process and the physical boards are part of our training within our department.

Whlie I completely agree with the fact that physical cards are the best, I am afraid that teams will start hating updating at two places, in the card as well as in JIRA, if you are using JIRA for sprint burn downs.

Initially everyone starts with physical cards, but for larger projects and distributed teams, this can become a pain.

Renjith,

The extended teams already only use the virtual board. I update the physical board for them. The team members stand in front of the board during our stand-up and don't mind moving the card over to a column. All burn down hours are recorded in Jira. It seems to be working at the moment and we will eventually will migrate to a projected virtual board, but not my call at this time.

Yeah, it makes sense. Keep a tab on that you said 'I update the physical card', so that in future it does not become like the whole process of migrating to scrum just becomes your headache without an actual involvement from team. Keep the team also responsible for maintaining this.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 9 hours ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

149 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you