A Version in JIRA can represent a software version and at the same time a child version under the same can represent as SPRINT. Can we add some identifier/category field on version screen so that we may identify Sprints from versions without looking at the version name(version name as version 5.0 or Sprint 1 is a very subjective judgement)
There isn't a way to differentiate versions, except by using different names.
This is different in GreenHopper 6, where sprints are not versions but instead a unique field only available ibn GreenHopper.
What were you hoping to do if you could differentiate versions from sprints?
If I could differentiate I would say that items in my version but not in any sprints are yet to be planned in microdetail. Items under the version but planned in Sprints(child versions inside main version) already are the ones wherein all the groundwork is done, scope is clear and acceptance criteria are known and one can just get down to do and close the delivery defined in the sprint.
Having said that, if I need to attach a reporting tool ( my own) and fetch data from JIRA, I could etxract easily without having to bother what naming convention any team has used to mark Sprint scope or Version scope.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...
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