JIRA currently let you add three extra fields to show up on Kanban board. Which is global for all issue types in your Kanban board. Is there any work around to customise this for each issue type ?
In my use case. I have Epics, Stories and Sub-tasks in my Kanban board. Ideally I want Custom fields I have created to only appear under Stories and Epics. Not on Sub-tasks.
The way I went about this was, i created a custom field and add it to Epics, Story fields schema and kept it way from Sub-tasks schema.
And then add the special custom field to the Kanban board using 'Card Layout' under Configuration. Which automatically add word 'None' to the Sub-tasks cards. Which is not great
No, a board is supposed to be a consistent view of a set of cards, so you can't do that. You can, of course, place fields that only belong to some issue types on cards, but that means an empty space where issues that don't have that field.
I'd question why you have such different fields on a board.
Thanks for confirming. Its not actually empty space. It adds the word 'None'. Which give the impression data is missing.
Example scenario is use of Storypoints, I want to have storypoint estimated for epics and stories. And for sub-task I wouldn't want any estimation as sub-tasks. And another example is stories vs bugs.
And if your kanban board have both of these issues types, you will run in to above problem. Anyways, Jira has very neat filtering mechanism for organsing the board with multiple issue types.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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