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.
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs