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: https://support.atlassian.com/jira-service-management-cloud/docs/link-a-form-field-to-a-jira-field/ 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?
Thanks,
Przemek
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:
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:
Thanks,
Przemek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.