Generally you don't. Could you explain what you are actually trying to do though, as that could lead us to a better answer than the handful of total bodges I am imagining.
Sure. Within a particular project we want certain number ranges to coincide with particular issues. For example, hardware issues get a number in the 5000's while software issues get a number in the 6000s. I know this could be differentiated via separate issue types in the project, but I was asked to investigate further. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, there's no way to do that at all. JIRA uses the next free number, and it never goes back to reuse numbers, even if you've skipped them. It's a pretty horrid way to differentiate between hardware and software, it sounds like an inherited bodge from a system that wasn't designed as a proper issue tracker. I'd take the opportunity to drop the idea from your processes and do it properly, with proper issue types or separate projects.
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.