The target is to see a new generated ticket like:
PRJ-0001 instead of PRJ-1
Hi @Roberto Raimondi ,
There is not way on how to fix that on JIRA cloud. Although it would be possible if you are using JIRA Server
Ciao Jason,
thank you for your answer.
So you suggest me to migrate from Cloud to a local Server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Depends how much you need this. Moving to server requires some maintenance from time to time. Server upgrades, add-on updates, etc....
I personally prefer server much more than cloud because you have full control on what you want to customize on JIRA.
When it comes to costs, if you are more than 50 users, server would be the best choice.
cheers,
jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Er, implementing this on server is not a simple flag or setting (that Cloud doesn't use).
It would need you to rewrite the code that generates the number used, either by changing the database to use a string for the issue number (and hence rewrite all the code that expects it to be a number) or by rewriting everything that uses the number such that it understands to convert between the 0-padded string and the number at every point. You're going to need to hit code that handles displays, inout, searching, and indexing.
You would render your Jira installation instantly unsupported by Atlassian, you would have to re-do the analysis and re-coding on every upgrade, and some of the apps (including Atlassian's own internal ones) may well be broken by this as well.
Your best option here is to forget it and just educate your humans that Jira does not have leading zeros in its keys. They're not much use in real life anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No need to mess around with project keys. There is a good add-on called “Automation for jira” i like to use. Just create a custom field and set up a counter with required padding for each issue created. That field can be added to notifications such as emails or chat channel alerts and can also be clickable my mapping it to the {{issue.key}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pointless though, as the field won't even be a link to the issue, won't be used for issue linking, won't appear in most places where you are interested in a key and won't be particularly searchable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.