I'm using JIRA 4.0.2 and found sometimes it can generate two different issues with same key.Such as: Key SIS-001 linked with two issues (issue a, issue b) and both of them are linked with (issue a) , others will never achieve. How we can avoid this and about exist issue data how we can correct it ? BTW we just bought latest version , the issue it will still happe in new version ?
Hoping that an upgrade will magically fix a problem you don't understand is not really a good approach. It might work though, if the upgrade causes you to accidentally fix it (by removing the plugin or code change you've got that is causing it)
To upgrade, start with https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA
Make sure you read all the release notes for at least the mid-level updates (4.1, 4.2, 4.3 etc)
You'll need to analyse your usage of ALL plugins (especially as you have a problem, it's likely that you want to remove as many as possible to try to fix the problem)
You should probably not jump straight to the latest version - from 4.0, I would consider a move to 4.4 or 5.0 before going to 6.1
This generally won't happen in any version of Jira unless there is something very wrong - most often a plugin doing something bad.
There's no way of knowing if it will happen in other versions until you can establish why it's happening in your current version. Start by looking at the circumstances of duplicate creation - what or who is creating the issues and how?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot