This may or may not be a unique situation, so any creative suggestions on how to solve this would be appreciated.
With that in mind. Let's use an example issue where we wanted to create a task in JIRA for our forty ships,
That one issue, is actually 40 issues. Because we want each ship's assignee, to produce a unique rack elevation. 40 drawings, from 40 different assignees.
From an oversight perspective, we would prefer see in the JIRA board which ships are done, and which are not, etc.
All very well conceptually, until we wear the shoes of the requestor. As the requestor within JIRA, must we:
Or is there an easier way either through customization, workaround, addons, that people are aware of that can do this in a more user friendly manner. Maybe there has not been the exact issue reported on here, but even something could marginally help would be better than what we have now.
My worry is if we have to create an issue 40 times and fill in every field 40 times, we'll naturally default to just e-mailing the ships the task and ask them to reply once done. A process I'd prefer to move away from...
Using some scripting tool like script runner you can achieve this kind of behavior, for example:
Then you can improve this logic by changing some fields based on the assignee, that should be possible too.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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