Sharing issue index between different projects

[Doron Cohen-Netzer]

We have in our organization several projects to manage products bugs.

one project is a shared library that used within the others projects.

When we moving issue from one project to another, the issue index is changed

This is not convenient, as once bug is open by the test engineer, and moved between the projects, the index is changed and make difficulties to track it.

For example - 

When issue was created in one of the project, it will get the index: Index-1000.

If the issue moved to a different ptoject, it will stay with the same index: Index-1000

thanks

[Aron Gombas _Midori_]

Although the primary identifier of JIRA issues is the key, which is in the format "FOO-123" (and therefore changes when moved from one project to the other), they also have an integer identifier like 10234! This latter does not change with moves, so you could refer to your issues like as "10234" and not as "FOO-123".

The problem is that the integer identifier is (deliberately) less visible in the Jira web UI. But, if you move your cursor to the "Edit" or "Comment" button at an issue, you can see that the URL ends like "?id=53058".

If you like this idea, I guess it would be pretty easy to a custom field (with ScriptRunner e.g.) or web panel or something that displays this in a read-only mode. Maybe there is something already available...

[Doron Cohen-Netzer]

Thanks!

This starting to sounds like reasonable solution.

Can you please provide more info regarding this identifies? Is this have a name and exposed in REST-API to can be automated and added to the Jira issue description?

Doron

[Doron Cohen-Netzer]

Thanks for your comments!

There is a logic behind such request - 

Think on a product built from different software pieces that even can be released and deployed independently.

Still when bug is open, it opened on the entire product, or at least on the first suspected software. but when the debug shows that the issue in resides in a different package. So the next step is to move the bug to the second project. Once done the issue key was changed. In case that the issue again needs to move to the first project, then the key changed again.

In those cases it's hard to track the issue where all the meeting and discussion are done while mentioning the issue key (easy to mention the number instead of the entire bug description)

Is there an option to open a project that will use only for the issue-key, but all others info and records, will be done in others projects?

Doron

[Nic Brough -Adaptavist-]

What you call the "index" is called the "issue key" in Jira-English.

The definition of this key is "sequence within the project the issue is in".  So an issue in a project with a project key that is not in the project is nonsense.  The key has to be <current project>-<sequence>

The whole of Jira, and all its add-ons make that assumption and there would not be any point in having projects if it were different.

Jira does track moves though.  If you search by an old issue key, or go to its url, you will land on the issue with the new key

[Gregor Kasmann_Actonic]

Hi Doron,

Unfortunately it is not possible from "vanilla" JIRA. You may use Linking between issues from different projects, to track relations. https://confluence.atlassian.com/jiracoreserver073/linking-issues-861257339.html