How to offer a field only to specific issue keys

Question

Hello guys,

I am currently thinking about if there is a possibility to limit a field on a screen to be presented only on specifc issue keys.

We have an issuetype called "Test", which was created about 200 times.

Now I want to have the possibility to provide a specific field only to the issue keys Test-1, Test-3 & Test-4.

I am not sure if this is possible because adding it to the screen would lead to an offering to all issues existing and new ones.

Maybe there is a possibility with Scriptrunner.

Mark Segall · Answer

My thought is that the simplest approach is to create a new issue type/screen for those specific issues.  They can share the same workflow as your Tasks to reduce administrative overhead.  It's also scalable.

Tobias · Answer

Hey @Mark Segall

what would you suggest?

I thought about two possible solutions:

* Adding a behaviour like @Radek Dostál mentioned above 
* The users want to have the possibility to edit the light status at every time. That means that from my end I would add transitions to every status itself and add a condition which includes the issue keys of the desired issues. Than I would add a screen with the mentioned fields.

What would you prefer or do you have another solution?

Tobias · Answer

Hi @Radek Dostál

I already thought about putting the field on the mask, but it is a select field. The default value is yellow (field for a project status). As it only refers to certain projects (in this example the same as activity types), the customer asked me whether it is possible to restrict the field to the issue key.

The setting is currently 10 issue keys and I would map the issue type of the request in the description of the behaviour for traceability.

I just thought about setting a lable like "Tracing projectstatus" and set this as a condition for a transition called "Light status" where I can provide the fields. That would lead to the same solution I think but without customizing Jira that much.

I am very unhappy with the solution myself but my hands are almost tied here. What would the query look like if it were not just one field but several?