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; } } }

Changing issue type - how to configure the "update fields"

Simon Sahli

Hi Community,

question related to when you are changing from issue type to another within the same JSM project.
It can happen that customer choose the "wrong" issue type and therefore the agents must change it to the correct one.

When they now change from one issue type to another they come there is a "Update fields" section and here is the first question.
Can I configure which fields I want to display here?
Ideally I can display certain fields here that MUST be changed to the correct value before the issue type change gets completed so the right data is place directly.

In relation to that, whenever somebody changes the issue type the request type stays the same and an error appears.
Ideally I could define a default request type per issue ype that should be taken for these issue type change use-cases
Is that possible?
Or what do you recommend here?

Thanks for your expertise in advanced.

Cheers,
Simon

Accepted answers

Patrick Tripodi_5345va

Hi Simon,

Unfortunately no to both but I use a workaround.

I have an automation set up that triggers on Field Value change being Issue Type and then a big If/Else statement to check if its the issue type, if so then set the Request Type.

All comments

Patrick Tripodi_5345va

Simon Sahli

Hi @Patrick Tripodi

but do you know why the "Group" field is shown in the "Update fields" part when changing the issue type?
Like there must be some kind of logic, why this field is shown there, but not other ones, right?

That is a good idea, an automation rule with the "Field value changed" and "Issue type" should solve the situation!
I can define at least the defaults I want to have for the different issue types and then I will just tell the users to manually update it afterwards when they want to differ from the default...

Patrick Tripodi_5345va

Hi @Simon Sahli ,

This would have to do with custom field contexts.

So Group probably is restricted to 1 or more issue types, but not including the source field. So in Group custom field contexts, there is a restriction to only appear on "Customer Support Case" (plus more maybe but not including your source issue type)

This is my assumption without seeing the field contexts though.

Simon Sahli

Hi @Patrick Tripodi

you are absolutely right, the "Group" field is one of the few fields that is only assigned to some issue types in the relevant project, but not to all of them, whereas the other fields are pretty much all assigned to all issue types available.

Ok, then I know that the group field is shown due to this configuration.

Would be nice to be able to define, which fields should be defined when changing from one issue type to another, but I guess Atlassian does not have the functionality for that.

I will just implement the suggested automation rule solution and just share the knowledge around this with the users.

Thanks again!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management