How can I customize my issue collector form?

[Deleted user]

Hello everyone,

I am new and happy Jira administrator. What a great project management solution!

I have been using Jira for 2 months and I managed to put a lot of things in place with: Ticket types, workflows with controls, etc. With my team, we are working in sprint mode and we can say that we have succeeded thanks to Jira in implementing Scrum within the team.

The difficulty that I encounter today is the implementation of issue collector.

I started by creating a specific type of issue that I called "Suggestion" and then I created a specific screen.

My Issue Types

The list of my screens

The fields on my screen for suggestions

The problem I am having with the issue collector setting is that I have a field (scope) that is mandatory for the other ticket types we use (bug, story, task and subtasks).

This field is displayed in the issue collector form (see screenshot below) whereas it is not present in my page specific to my Suggestion type issues (see screenshot above).

Configuration screen of the collector issue where we see that after selecting the "Suggestion" issue type, the undesirable "Scope" field is displayed.

To complete the information, here are the other elements of my configuration:

--

------

----

Except for workflows, I'm not familiar with schema configuration.

Is there a kind soul here to explain to me in order the main steps that I must take to allow me to solve my problem please? 

Brice

[Jack Brickey]

Hi @[deleted] , welcome to the community!

thanks for all the details on your post. However, I wonder if you could simply state your question. Are you asking how to make the Scope field required on one Issuetype? Or something else?

[Deleted user]

Hello Jack and thank you for your feedback!

This configuration does not depend directly on the parameters in issue collector but on the schemas.

I have the "Scope" field which is mandatory for issues of the type: Bug, Story, Task.

I would like this field not to be mandatory and not displayed for the "Suggestion" issue type that I use exclusively for the issue collector.

• But I have no idea how to achieve this?
• Do I need to rephrase my post question?

Brice

[Jack Brickey]

So what I would do is to remove the field entirely from your Suggestion screens. I assume the Scope is required at Create or is it at some other transition? Assuming it is at Create for your other types then consider creating a Validator in the Workflows for those types on the Create transition. In this solution you do not make the field required in the configuration scheme.

The other solution is to have unique screen schemes and field configuration schemes for your Scope type allowing you to not make it required for the one type.

[Deleted user]

Hello Jack,

1. In fact, the "scope" field is not present on the screen of my "Suggestion" issue type. You can see it below:

2. The "scope" field is present on the screen which is shared by my other issue types (bug, story, task and sub-task).

3. The only view field configurations is the default one . On which I configured the "scope" field as mandatory. and i have none field configuration schemes. You can view my configuration from the screenshots which are present in my question.

4. Are you suggesting that I disable the mandatory "scope" field in the "Field configurations" settings so that it is not mandatory? And to make the field mandatory only on the transition of WFs of the issue bug, story, task and sub-task types?

5. For the other solution which consists in having unique screen diagrams and field configuration diagrams, how can I set this up from my current configuration please?

Thank you for your time, I'm sure the answers to this ticket will help more than one ;-)

Brice

[Jack Brickey]

Hi @[deleted] ,

so if your goal is to make a field mandatory for one (or more) issuetype and not another within a project then you simply use different Field Configurations for your issue types and create the field configuration scheme from them.

To help with this point here is some instruction directly from the product:

A Field Configuration provides the ability to change field behavior, it essentially tells Jira how to handle a particular field. For example, a Field Configuration can be used to hide a field from all input screens and views, or to make a field require a value every time it is edited.

Field Configurations are activated by placing them into Field Configuration Schemes, and then associating a scheme with one or more projects.

Field Configuration Schemes map Field Configurations to issue types. A Field Configuration Scheme can be associated with one or more projects, making issues in these projects use the Field Configuration mapped to their issue type.

---

You may also find this document helpful - specify-field-behavior 

[Jack Brickey]

BTW, here's a bit of information on when you would use a validator and when you would use field configuration.

Validator - this method is useful when you want to add a field required validation after creation of an issue during a subsequent transition. The most common use case is when transitioning an issue into a done status where you want to require the Resolution Field.

Mandatory field - Setting a field is mandatory in the field configuration really should only be done when you always require that field from the very beginning. That field must be present and must be filled in. In this scenario it is important to ensure at the field configuration is only applied to those issue types where are you truly need or want the field to be required.