The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Close screen items are different depending on Issue Type

DIno
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 24, 2020

(v.8.5.4) Our CLOSE ISSUE screens displays different selection items depending on the ISSUE TYPE selected. 

Drop-down selections in the Close Issue screens appear to be either standard selections for some Issue Types (ex. Summary, Resolution, Time Spent, etc) or customized selections in other Close Issue screens for other Issue Types (ex. Summary, Helpdesk Status, Helpdesk Root Cause, etc).  

Workflow, Workflow Schemes, Issue Types, Issue Type Schemes, Screen Schemes, Validations, and everything we checked are exactly the same between the two selected issue types.  

Where are the Close Issue screen items customized and how can they be propagated across different screens? 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 25, 2020

The screens you see as you move issues through a process are all "transition screens" - they are determined by the workflow.

If you are using the same workflow, then you are using the same screens for each action.

Some fields those screens select and present to users are however subject to some other configurations in the projects.   For example if work logging is not available in a project, then the time-spent stuff will look different.

Summary is plain text, it won't have "customised selections", helpdesk status is drawn from the request attached to an issue in a service desk project (which could be different to all the other service desks).  Root cause is a custom field, so it can have a different context by project (different selection list for example)