Some time ago we started using JIRA for software development and adapting it to our development process, which requires attaching files to JIRA issues in some projects.
It has become quite efficient during issue investigation, as the developer can always see log files, screenshots, FD or SRS documents in the issue or task.
After a while we encountered a disadvantage of this method, as each issue contains at least 7 or 8 files. When the developer opens the issue he sees quite many files and navigation across them becomes rather frustrating.
We tried to add a special prefix for different file types, to indicate that this is FD or SRS and so on. Prefix has allowed us to get a better view of attachments while sorting by name, but not all empoyees follow this and not all the time they have time to add this prefix.
So my main problem is there any way to aternate view of attachments and see the attachments in groups, e.g. SRS - contains any documents related to specifications and so on.
I hope that the community has any ideas or practices how to cope with this issue.
Any help or piece of advice will be appreciated.
As of https://jira.atlassian.com/browse/JRA-4925 - as I see it is a long story, and I don't know existing plugins with attachments as custom fields. But you can develop/order your own plugin that will satisfy your needs: see https://developer.atlassian.com/display/JIRADEV/JIRA+Plugin+Guide and https://developer.atlassian.com/display/JIRADEV/Custom+Fields+in+JIRA
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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