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

How to Change JSM Default "Request Type" And odd Pre-Select Bug on Creation?

Calvin

Hi all I seem to have two problems here but they look to be related:

1. Every time I click on "[System] Service Request" issue type, it automatically goes to AAA Request type, when I want DDD Request Type first. It seems to ignore the choice I use in the Features area.

2. For "AAA Request Type" the portal uses "use default value and hide" for a certain field. BUT I find its also ticking that field in the backend too when it automatically sets it to "AAA Request Type". So when I updated it to "DDD Request Type" the field in AAA is the wrong value.

EDIT

It looks like for point 2 this hapens only for Checkboxes. Tried it again in another instance with different values. Same thing happens?

(Q1) - Video of problem - Request Type Defailt - MIsmatch - 2mb.mp4

(Q2) - Video of problem - Request Tpe - Wrong Default Value.mp4

Accepted answers

Marc -Devoteam-

Hi @Calvin

I see your issue and I can reproduce it. I suggest to raise this at Atlassian Support as a BUG.
I don't have a setup like this, so I can't tell.
This I first need to build.

But as both seem related to the the request/issue type feature in a JSM project, I would think it's all related to this feature.

All comments

Marc -Devoteam-

Hi @Calvin

I see your issue and I can reproduce it. I suggest to raise this at Atlassian Support as a BUG.
I don't have a setup like this, so I can't tell.
This I first need to build.

But as both seem related to the the request/issue type feature in a JSM project, I would think it's all related to this feature.

Joseph Chung Yin

@Calvin -

Are you using the following setup?

1) You have a WF for the issue type that supports your specific request type, and in the WF (at creation time), it is firing a post function call to update the request type?

2) Do you have other third party add-on that may impact the actual value of the Request Type field?

What do you mean by clicking on the issue type, and default it to "AAA Request Type"?

If you have both AAA Request Type and DDD Request Type, then there should be two separate entry points from the Portal UI.

Please advise.

Best, Joseph Chung Yin

Calvin

Hi Joseph, Thanks for your comment, to answer your comments:

1. Not that I know of. I added a video in the above of a completely new stock instance and project and I see the same issue. I created a completely new instance to ensure there isn't any impact from anything else.

2. Similar to 1. above, I added a video of what the problem is. I also tried it in a completely new instance with no addons at all to ensure there is no impact or changes.

Note in the video I used BBBB instead of DDDD.

Calvin

Thanks friend, I think your right, it may indeed be an actual bug for Atlassian support and not something I've done.

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