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 there any way the view field can be different before and after the issue is submitted?

Moon_wrhy9h

Dear community members,

I need a help how to show different fields before and after the issue is submitted?

Am I required to create two issue types, or is there another way?

I would appreciate it if you could give me an idea.

Please assist and advise on this matter.

Thanks a lot.

Best regards,

Moon

Accepted answers

All comments

Filipe Guedes_j62fzj

Editing my answer as it isn't helpful for the OP or future users with a similar question.

John Funk

Hi Moon,

What is your exact use case? It is a little hard to understand your request.

Nic Brough -Adaptavist-

Please stop using AI to generate answers - they are usually wrong, and at best, unhelpful.

This answer does not help, it does not solve the presented problem and it does not explain why the poster is asking to do something pointless.

Nic Brough -Adaptavist-

Please stop using AI to answer questions. It has given you a completely wrong answer, and not tried to explore the question properly.

Filipe Guedes_j62fzj

Hi Nic,
Edited my answer. Wasn't my intention to provide a wrong answer. I saw this as a topic that I wasn't aware of and tried to educate myself and help someone else, but I understand your point.

My apologies and have a great day.

John Funk

Where did you go @Moon ?

Rick Westbrock

It sounds like you just need to have separate Create and View/Edit screens each of which has a different set of fields. We commonly do this to keep the number of fields to a minimum on the Create screen as that it makes it easier for the user to get the issue submitted then they have access to more fields on the View/Edit screen to set later.

We also have a few use cases where a field is only on the View screen but not on the Edit screen so to edit the field the user must trigger an automation rule or a self-transition in the workflow (which has a transition screen) in order to edit the field. We typically do this for fields where only members of a specific group are allowed to edit the field.

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-desk

jira-service-management-cloud

jira-service-management