Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,232
Community Members
 
Community Events
176
Community Groups

Attribute or field local to each Kanban?

BACKGROUND

I have one Jira project, type "Software", with lots of tickets/issues coming from a variety of sources.

I have three kanban boards to be used by three persons, representing three stakeholders.

Each of these persons will drag and drop cards in his/her individual kanban, to express ranking according to the stakeholder view.

Ranking done in one kanban is local to it. Dragging and dropping in one kanban, does not influence ranking of cards in the other two. So far so good.

QUESTION

Besides ranking, is there any other property/entity/field,/attribute/whatever, that is local to each kanban?

(I tried "Add flag", but apparently flags set in one kanban, are set in the Jira project tickets/issues, and consequently they show up across all three.)

BR, Anders Skelander

1 answer

1 accepted

4 votes
Answer accepted

Hi @Anders Skelander 

The reason why flagging the issue shows across all 3 kanban boards is because it's specific to the issue, which is being shared between all 3 kanban boards.

Similarly, ranking settings are board specific, meaning you can choose how you want to rank the issues in your board — as an example, your board may have a ranking setting of ORDER BY Rank ASC.

If you make any changes to any field within the issue itself that is being shared between the 3 boards, then those changes will be seen in other boards. So no, that is not local to each kanban board, because the change is occurring to the issue's attribute (i.e. impact is issue-specific), not board-specific.


Please keep in mind that a board is just a visual representation of how you want to display your issues based on the board's filter in the form of a JQL query. 

 

Regards,
Hamza

Thanks Hamza!

So are you saying, there is nothing else, board-specific, that could be used instead of flags?

BR, Anders Skelander

Not really. Aside from Scrum boards (which make changes to the 'Sprint' field), Agile boards are mainly just "views" that sit on top of projects\issues, sort of similar to dashboards.

Like # people like this

Thanks! So the implicit ranking is the only reasonably board-specific property.

BR, Anders Skelander

Suggest an answer

Log in or Sign up to answer