With the current ID scheme of <project key>-<sequence in project> for all issues, it becomes difficult to identify issue types and hierarchies outside of Jira.
Is there an alternate naming scheme that we could use (for eg., <project key>-<epic key>-<story sequence in epic>) to help with the above?
The built-in Issue Key field will not solve this for you, as it has a hardwired format.
But, it is actually fairly easy to solve your use case! Consider this:
The ID numbers themselves do not provide this kind of information. This is because at anytime an Epic can be changed to a task or vice versa.
It is up to the external sources to have this ability.
Take Smartsheets for example, if you have the Smartsheet plug in it does this and is able to identify the issue type. If you use the API you can pull this information from the API which is how it is identified.
So if the tool you are using outside of Jira isn't identifying it you most likely want to talk to that tool on how they can pull the information as Atlassian does allow for it, but the tool would need to be making a call for issue type
👋 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...
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