I have set up Jira the following way:
Epic = Test
Issue = Test Module
Multiple test modules make up a test. Sometimes test modules are included in more than one test. Can I add the same issue to two Epics or two Versions ?
The Version/s field seems to indicate multiple versions are possible but I can't find how to add and issue to multiple versions.
One Epic per issue but you can have multiple versions per issue. The idea of Version/s is to convey which versions an issue was fixed/added to. Example: lets say I have 1.1, 1.2.3 and 1.3.1 live in the field and I'm working on release 2.0. A customer reports an issue in 1.2 and I plan to address this issue in 1.2.4, 1.3.2 and 2.0. All three of these releases can be added to the Version/s field.
If you are using the Fix Version/s field you simply select the field and start typing. A space will equate to completing the version at which point the next entry will be a separate version. If the release is predefined it will autofill and you can select. If you do not have the version predefined it will create it so be careful that you don't create nonsensical release names.
Thanks again Jack. When you say a space will equate to completing the version. My aim is to include one issue in two versions (tests) which are both ongoing (not completed). I'm trying to establish that a developed module is included in multiple tests. This is possible ?
Sorry poor choice of words. The space is the separator between version. The only way to 'close' a version is on the release screen. Yes you can designate any number of versions in this field regardless of their release status (released, in progress, planned). This last fact is what gave me challenges in the past since, w/o knowing the status of a release some unsuspecting audience wouldn't know if the fix was in a release w/o knowing the status of the release and from the view screen that isn't clear. The release view is a good way to help with this as it shows what is in a release and the status of the release. Of course this relys on someone keeping that info up-to-date.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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