Custom fields by issue type

[Mo Omar]

Hi Guys, 

I know some of you have answered this question a few times before, but hopefully one of you experts can point me in the right direction. I'm good for it and will pay it forward once I know it myself :-)

by the way JIRA's 'knowledge base articles' appear daunting and appear not in order of prerequisites for any beginner. 

<----------------------------------------->

Problem I have:

1. I have a new issue type 'Change request'. How do I add custom fields only when the user selects this issue type from the drop down list. In this scenario bug/task/story etc all behave as default fields .... however when users select the 'Change request' issue type I want the user to fill custom fields associated with change management (informed by our internal Change Management process).  

2. How do I make those fields either a drop down, list of choices, yes/no, text, select JIRA staff member (owner) etc. 

3. How do I make those fields smart i.e when user fills-out/selects this option for this field alert so and so... or when user fills out this part make them also fill out this field. (specify field behaviour) ?? 

4. How do I make some of these fields a requirement before the user can 'create' the ticket (submit). In other words make it an asterisk* field (is this accomplished only using Java script or is there a different way of doing it?)

5. Finally how do I alert 'The Change Manager' of the ticket once it has been created. 

Your responses are eagerly awaited but also highly appreciated.

Many thanks, 

Mo

[Meg Holbrook]

Hi @Mo Omar - Some things where my opinion might deviate a bit from Romer's:

#2 when you add a custom field, you can choose what kind of field is being added. If you select to create a dropdown, you will add dropdown options. A user-select custom field will allow user choices, etc. Unfortunately, with a vague question comes vague answers. The more specific you are, the more helpful we can be. 

#3 I find that the Automation for JIRA addon is very useful for adding functionality to out of the box automation. You could create a trigger where, if an issue is update, and a certain field value changes, a trigger will occur. For example, if I wanted to notify my service desk technician that someone selected Yes on the 'Do you want Ice Cream?' custom dropdown, an email would be sent to the person I indicate would fulfill that request. Use cases are endless really.

#4 agree with Romer, but keep in mind that required fields will absolutely break your email collector if you have one set up. Make sure all your users are utilizing the portal if you proceed  with adding requirements. 

I agree that the how-to articles on the community are largely topical, and have no 'set order'. This works best for users who are already trained on the system but may need a refresher on certain items or are going over something more abstract. I highly recommend taking a training course through Atlassian University to get you on your feet in terms of training. 

[Mo Omar]

@Meg Holbrook you're an absolute gem! + Your JIRA knowledge exceeds your beat-boxing abilities ;-) 

A  of follow up questions on one of the points; 

3# any recommendation for an 'Automation add-on', went on to the market place and was bombarded with choices; just a link will do. 

Or does this depend on the type of functionality required ... silly question but still a Young Jedi out in this JIRA world. 

Many thanks!

Mo 

shout out to @Romer Ventura as well

[Meg Holbrook]

Hey Mo, the addon is actually called Automation for JIRA

This addon will take care of 90% of your needs, and they're adding new functionality pretty regularly. 

[Romer Ventura]

Oh man, that's a lot of things you're asking for....

1. You can add/remove fields to the create/edit/view screens associated with the change issue type for a specific project. 

2. If it's customer facing side of things, just create request types with whatever fields and issue type

3. I m not sure i understand this, but you cant have dynamic form. you may be able to set some fields via automation, but not sure what you're asking for

4. Edit the request type and mark whatever fields as required. 

5. This is done at the workflow level