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:Ā 

Make a fields Show/Hide depending on creating request types in the portal.

veereshpatil0101
June 23, 2023

Make a fields Show/Hide transition screen depending on creating request types in the portal.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Deepak Jain
Community Champion
June 23, 2023

Hi @veereshpatil0101 

Welcome to the Atlassian community !!

If you want to Show/Hide fields depending on request type, it is simple to do so. You can go to your project settings (It would require project admin permission). And on Request types, configure the Field you want to show, and remove the field you want to hide.

If your requirements is something else, kindly let me know.

Thanks !!

Deepak Jain
Community Champion
June 23, 2023

So in short, you can setup a different screen for each issuetype/request type from project setting.

veereshpatil0101
June 23, 2023

Hi @Deepak Jain 

Show/Hide fields depending on request type in the transition screen.

Deepak Jain
Community Champion
June 23, 2023
Like • # people like this
3 votes
Joseph Chung Yin
Community Champion
June 23, 2023

@veereshpatil0101 -

Welcome to the community.  Please provide more clarification on your exact ask.  I do agreed with what @Deepak Jain provided, however are you referring the pop-up screen associated with your issue's WF as the issue transition into different statuses via the project UI based on the request type where the issue is created in the portal UI.

Keep in mind that ScriptRunner for Jira's Behavior component is still being enhanced by the vendor for the CLOUD env, so hiding/displaying fields functionality are still limited.  On the other hand, this is an excellent add-on for any Jira/JSM env.  The Behavior component is very robust in the DC env, and the vendor is continuing their effort on providing all the DC env functionality to the Cloud env.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

TAGS
AUG Leaders

Atlassian Community Events