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

Is here a way to set a MAIN CONTENT field to be invisibile unless it contains a value?

Shaun McGuire

I'm looking for a way to have a couple of additional text/paragraph fields in my Jira issue screen that should appear in the main content area (Not Details or Hidden Fields sections). Ideally they would appear just under the standard Description field, but ONLY if they have a value (which would come from a different process/automation).

Is there a way to have such a visibility option and NOT have to move the field to the Hidden Fields section, which is not the same area at all.

Accepted answers

Marc -Devoteam-

Hi @Shaun McGuire

Unfortunate this is not an option.

Main content section fields will be visible even if not set.

You could look at behaviour app to hide this kind of fields based on content in the field or not.

There is an open issue on this topic you can vote for, JRACLOUD-76717

All comments

Marc -Devoteam-

Hi @Shaun McGuire

Unfortunate this is not an option.

Main content section fields will be visible even if not set.

You could look at behaviour app to hide this kind of fields based on content in the field or not.

There is an open issue on this topic you can vote for, JRACLOUD-76717

Shiva Kumar Hiremath

Hello @Shaun McGuire ,

You can configure the issue screen,make the fields hidden only when empty.

Hidden empty.png

Marc -Devoteam-

Hi @Shiva Kumar Hiremath

As mentioned in the post by @Shaun McGuire

This is about the main content section of the issue, not the issue details section of an issue.

Please read the post with attention

Cael Metcalfe

You can use different Request Types with differing Issue View configurations, and have Automation change the Request Type based on those fields being updated and whether they have a value set.

Waste of automation though and requires a Request Type per possible configuration of shown/hidden fields, so not very practical.

Just showing that it is possible.

If you use transitions and workflow screens to set field values, then Post Functions can update the Request Type for you without automation (use Validations on the transition to make the fields required too)

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud