Hi! 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. 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?

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

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

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; } } }

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

Max Ålander

Hi!

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?

Accepted answers

All comments

Sreenivasaraju P

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.

Fabio Racobaldo _Catworkx_

Hi @Max Ålander ,

welcome to the Atlassian community!

Please take a look to the following thread https://community.atlassian.com/t5/Jira-Software-questions/Parents-ticket-in-history-only-showing-ID-Can-I-get-more-info/qaq-p/1853649

Max Ålander

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

Max Ålander

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.

Nic Brough -Adaptavist-

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?

Max Ålander

@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.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud