We are considering trying & using the Issue Collector to enforce a policy, so as to compell users to enter a few set of information in some tickets for a project, without having to modify anyhow the attributes in the JIRA project, so as to keep it very simple. It means, in the issue collector, people would be possibly asked to enter a few fields, some of them being defined in lists of values, some being text fields, and in the end, when submitted, the jira ticket created would gather these pieces of information in the description.
Have some of you tried this? Any particular opinion about this? Again, of course, I know we could add attributes to this project, but we want to avoid that, as we try & keep all our JIRA projects standard, to make maintenance/upgrades easier :)
Thanks for your help
Frankly I consider this as an overhead to customize Issue Collector to collect data using fields and them join them all to the description. Rather have the fields in JIRA itself (as mandatory) and in turn in Issue Collector. It is the easiest and also easy for maintenance and upgrade.
Thanks a lot Renjith. I can understand your answer, however, I have to take into account my company policy, which is 'keep JIRA standard and simple', as all teams are supposed to use the same worflows/attributes, so as to make administration costs as low as possible. Any exception is to be justified. Thus, I was thinking using the Issue Collector would be a way to proceed (another would consist of adding some Velocity code to have a template for the description, but well, I'm not really fond of that).
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot