nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Show Assignee in Jira Issue Card

Matt Richards_q2q9cg

We are using a whiteboard to coordinate the work of multiple people. Going from stickies to Jira issues has been very helpful, and it's helping us move more of our process into Jira. The problem we are having is that once we have a Jira ticket shown on a whiteboard as a card, the assignee is not shown. This is causing confusion as we cannot tell which issue is applied to which person.

How do we show the assignee on a Jira Issue Card?

Comments

Jonno Katahanas

Hey mate - providing the ability for users to customize what meta data for an issue shows in a Jira Smart Link is something that we totally want to do! Just haven't got around to yet.

Common asks are for assignee (as you've suggested) & estimates like Story Points.

We may also look to provide some of these more commonly asked pieces of meta data as default information on a Jira Smart Link.

Matt Richards_q2q9cg

Customizability would be great, but it might be easier to simply match Jira's default. Issue type, priority and story point estimate would be valuable, but not as necessary as assignee in our use case, as I suspect it will be for many others. The purpose of the whiteboard is collaboration, and if you're obscuring the assignee things get opaque and unmanageable.

Perhaps it would be possible for you to easily add assignee to the current view to solve the existing problem and consider the larger task of customization to add functionality later?

Jonno Katahanas

That thinking makes sense. We've heard some asks for assignee, too. At some point we'll probably move towards providing customisability.

cc'ing in our designer @Daniel Simmonds who's been having a look at adding more meta data into the Jira cards.

Matt Richards_q2q9cg

Thanks. @Daniel Simmonds feel free to let me know if you need any additional insight into our use case. For what it's worth we feel strongly that this is needed, and in an ideal world you guys could quickly implement just assignee and not get into a larger, more time consuming, less valuable (in our opinion) project around customizability.

Welcome!

It looks like you're new here. Sign in or register to get started.