Kanban board custom fields

[Nem Lasica]

Hi all,

at my place of work, we use Jira. Our department (50 people or so) has created a Jira project and we have multiple boards as "filters" or "views" for our perspective teams.

For my immediate team (support based) I have created a Kanban board so that me and my immediate team can log "tickets" for issues. This works for us but I cannot figure out (if possible at all) how or where to customize the fields specifically for my team's Kanban board and our requirements. The fields currently seem to be pre-determined, many of which we do not need. We would like to be able to create custom fields with custom field names or perhaps fields with drop down options...etc

I am thinking here along the lines of SharePoint lists, how you can create your own sharepoint list with your own custom fields and views whilst still being part of your teams "workspace".

Can Jira boards be used in a similar way?

cheers

[Jack Brickey]

it is hard to say the best solution for you w/o really understanding your teams and work. However, my off-the-cuff suggestion would be to create a different project altogether of your team. While you could certainly add new custom fields and add them to the various screens (create, edit, view) in the existing project the results would be that the other teams would also see these fields furthering the 'does not apply to my world' situation.

Note that boards are simply graphical views of issue queries. The fields that are displayed when clicking on an issue are driven by the available fields and the screens they are applied to.

[Nem Lasica]

Hi Jack,

thank you for your response. What you said makes perfect sense. Perhaps you could shed some light on one more thing for me. I have noticed that there are different "Issue Types" eg. Epic, Risk, Story, Issue...etc and depending on which one I select when creating a new Issue, I get different fields. Could we perhaps create a new "Issue Type" specific to our own team? Unless of course I am not understanding the "Issue Type" correctly.

cheers