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
Community Members
Community Events
Community Groups

Portfolio: Show Assignee from JIRA Ticket (read-only)

I want to show the assignee for all issues in Portfolio scope view without mapping to scheduling features.

FWIW, I wasn't able to successfully get the mapping to work.  But in truth, we're not planning to use the scheduling features right now anyway.  All we're trying to do is allow our PMs to see all issues associated with a "Project" (<- aka Initiative) which span across several JIRA Projects.  The mapping seemed to apply only on certain issues, at certain levels, despite setting up teams with the appropriate members.

All we really want right now is to show "Assignee" like we do with any other custom field value, but it does not appear in the list.  Read-Only is perfectly fine for our purposes so we do not need to sync back and forth, nor do we need to use resource planning.

We just want to display the assignee as it's defined in JIRA.

Is there any way to make this happen?

1 answer

Thank you Krista, but no this is not what I am looking for.  It's close though.  We are not using the scheduling features and do not want to calculate resources using teams.  We also do not want to allow for editing of assingee via Portfolio.  We're looking for a way to simply render the Assignee in JIRA (read-only) and not to match up via a Team.

FWIW, I tried to get that to work but was not able to get it to map reliably.  Sometimes it seemed to map, sometimes it didn't.


Ahhhh gotcha. But it did match up sometimes? Was there anything different on the issue side when it did match up? 

Nope.  When it matched it was correct.  But it didn't always match.  I was thinking of creating a custom calculated field to simply write in whomever the Assignee as read-only is and may still try this.  

Thank you for the reply.

I am also looking for the solution to the problem which Ted is facing.

Does anybody have the proper solution?

I haven't implemented this yet, but what I am planning to do is create a custom field called "Assignee (Read-Only)" and copy the value of Assignee to there.  Then show this field as a custom field in Portfolio.  


We have the "Automation for JIRA" plugin, so I can watch this field and perform the copy whenever this field is updated.


I assume this will work, but haven't tried it yet.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

320 views 0 10
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you