nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Change Issue Type with different field configurations

Barbara Teuschler

Hi,

we have a project where we use the Issue Types Bug, Feature and Task. We have a common workflow for all those Issue Types but have the requirement that we need to have one field required for Bug.
I created a new Field Configuration for Bug and assigned it - this works as expected (whenever a issue is created or edited the required field must be filled out).

However an inline Issue Type change for an Issue is not possible anymore.
E.g.: I clone a Bug issue and just change the Issue Type to Task (inline).

I know that with "Move" we could move the issue to the issue type we want but we don't want users to have access to the move functionality (currently only admins do).

Is there another I can set this up, so that changing the Issue Type is possible for the users?

Thanks in advance for your help.

Best regards,
Barbara

Accepted answers

Alexey Matveev

You can have single screen scheme for all issue types but you would need Power Scripts Live Fields or ScriptRunner behaviours to hide a custom field depending on the Issue type.

All comments

Alexey Matveev

You can have single screen scheme for all issue types but you would need Power Scripts Live Fields or ScriptRunner behaviours to hide a custom field depending on the Issue type.

Mitchell Davison [EY]

Hi Barbara,

Is the field that you’ve made mandatory for Bugs visible on the other issue types? The restriction here is due to the different Field Configuration that you’re using for these different Issue Types. It may allow you to change the Issue Type if a value is set in the field, even though it’s not mandatory.

Barbara Teuschler

Hi Mitchell,

Yes the field is visible in all other issue types.

I just tried inserting a value and trying to change the type - it doesn't work.

Barbara Teuschler

Hi Alexey,

Could you please elaborate?

Can I use Script Runner to make a field required for a specific issue type without touching the Field configuration?

Alexey Matveev

Yes, you can use scriptrunner to make a field required for an issue type. You can either use behaviours or validators.

If you use a validator, you would add a validator to the create transition. In this validator you would check issue type and if it is a Bug, you would check if the required field is set with a value.

Alexey Matveev

But It could be done out of the box. You should create a field scheme configuration for the Bug issue type and set there the custom field required.

https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

Nic Brough -Adaptavist-

I'm afraid filling fields won't help.

You have to make the configuration for the two issue types you wish to switch between identical - using the same workflows and field configurations.

Senthilkumar_st7m76

Hi Nic,

I have a created a required for an Issue type story and its working fine. But below is the issue i face

Create story with all the details. Include acceptance criteria and Story points.
Move the story into epic and fill the epic details.

Note that after the successful move the epic has the acceptance criteria and Story points..

My question is, when i dint have EPIC Issue type to have the Required filed, Why i am getting the filed here when i move the ticket.

is this normal or an issue which can fixed?

Thanks in advance.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server