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

Change so I can see issue key instead of issue ID in issue history


When I go into the history of an issue to find out which parent it had previously I can only find the issue ID. This is the only place I see the issue ID and I'm not sure how to use it.

Question regarding Jira.png

It would be much more handy for me to have the issue key instead.


Is it possible to change the settings of our Jira instance or project to show the issue key instead of the issue ID?

2 answers

Thanks @Fabio Racobaldo _Herzum_ !
It helps me to understand how to use the issue ID, but not if I can change settings to show issue key instead.

There's no way to change the display,

The history is recording a minimum - the unique immutable id of an issue.  It might actually not want to be presenting the issue keys as they could be misleading or useless.

Imagine you've got these two linked: 

48415 ABC-123

49738 DEF-456

Now you delete ABC-123 and move DEF to XYZ-567

What would your history display?  The deleted one doesn't have a key, so I'd fall back on the issue id with "deleted" on it because you need something for auditors, but on the move, do you display the current ID, or what it was when you linked them?

@Nic Brough _Adaptavist_ I understand what you mean but for me it would be more useful with issue key in most of the cases.

What about @Sreenivasaraju P screenshot shown further down in the answers? There you can see the issue key instead of the issue ID.

Some places will display the issue key, especially if the issue is still there.

The issue is still there, but it only shows the issue id.

Hi @Max Ålander ,

Welcome to the community,


Could you please provide further details like are you moving sub-task of task (standard issue type) to other task  or are you referring moving task from epic to other epic. 


But in both case, it is reflecting issue key only, please mention your scenario.



Thank you got the warm welcome @Sreenivasaraju P !

In this case it was a story that moved from one parent epic to another.

What you show in your screenshot is what I want to see.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,660 views 37 46
Read article

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