I'm new to Jira,, and am building the architecture for a new interface requiring many hundreds of custom fields.
I'm wondering if there's a way to avoid the process of clicking "Add Custom Field" and manually clicking through the configuration of each field... perhaps a CSV sheet with each configuration item separated out, and imported through some kind of plugin? The same question would also apply to the creation/configuration of User Groups, Screen, Workflow Transitions, and even modifying Script Post-Functions in individual Workflow Transitions.
I'm desperately looking for any way to avoid plodding through hours of click-clicking, when I already have the logic and architecture determined. Help?!
You can accomplish what you're trying to do using a Jelly script:
That said, I'd highly suggest that you try and reuse as many fields as you can to keep the number of custom fields to a minimum. Having a large number of custom fields is a very common culprit for lots of performance issues, especially as things start to scale.
That does definitely make it much easier. And I see your point... I'm working with a pre-existing workflow to expand the current functionality. Definitely agree with you, there are more resource-efficient ways to organize a workflow without needing hundreds of fields. However, with my current time constraints I'm unable to restructure the workflow altogether to accommodate this.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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