Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira fields can’t be on a request form and a form at the same time - since when?

Hi Atlassian Team,

In our JSM project, I use forms to make a request form more friendly to our users. When I was setting them up about a month ago or so I made sure that linked fields were also visible in a regular request form after the ticket was created. 

Today I added one another field and after this operation, all fields disappeared from the regular request form. I wish I read the warnings more carefully. 

Before that time, fields that were linked were not visible in the 'create view' but were still visible after the ticket was created. 

I found this article today: and I am wondering why such change. Where exactly was it problematic? 

I also noticed this sentence in the article: "Required fields cannot be used in a conditional section" - and I still have mandatory fields in conditional sections. Does it mean that this feature is also removed? What is the justification for that?


1 answer

0 votes
Robert Wen_ReleaseTEAM_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 30, 2023

I don't think any of this is new.

The logic behind required fields not allowed in conditional sections is so that if the section is not triggered, you don't get into a situation where you can't create the issue because a required field isn't filled in.

The other thing you talk about where fields can't be in a form and the request form at the same time refers to the layout of the form as seen in the portal.  If a field is in your dynamic form, it doesn't make sense to have it outside that form in the request form.

Thanks but:

  1. I still have fields that are mandatory in conditional sections -> though I have not checked whether it is still possible to set them.
  2. As it appeared I still have one form where linked fields are only visible in the form part in the create screen (portal view) but are visible in the view screen in the request form part (again portal view) - but I am not able to set this up again.

In case you are wondering what kind of behavior I am talking about, please check the Summary field. 

I have highlighted the message I see next to each such field in the screenshot below:




Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events