Screen layout consistency

[karel_mellen]

How do we ensure consistent layout? For example, one of our most important fields is only present on certain request forms, where it's essential for client selection.

The issue arises because this field is grouped with other important custom fields on the service tab of the screen. This grouping only occurs unless the incident was NOT submitted through a request form that includes this field.

Consequently, this leads to inconsistent layouts within a single issue type, where the field's position is not determined solely by the screen configuration.

We're facing challenges with how the request form has become so prevalent in the cloud environment.

Can someone explain why there's been such a drastic shift compared to server behaviour?

Also, we have a concern about the 'requested participants' field, which consistently fails to appear on the create screen

[Joseph Chung Yin]

@karel_mellen -

When your project admins create request forms, did they follow some guidelines/standards to ensure the needed field is configured on every request form?

In regards to "Requested Participants" field, can you provide more details on the failures that it is not appearing on the create screen?  Are you referring to the Portal UI or Project UI when creating issues for your env?

Please advise.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[karel_mellen]

Hi @Joseph Chung Yin 

Thank you for taking the time to answer my question.

The issue is that this field is not always required on the request form. It's only necessary in specific situations where the customer must select the value themselves. Consequently, the placement of this field varies inconsistently, depending on which request form is utilized.

So in short, no *we* can not place the field on every request form.

Currently, both the Watchers and Request Participants fields can't be added to the Create Issue screen (and to the Request Type settings for Service Management projects). Reference: https://jira.atlassian.com/browse/JSDCLOUD-1511

Both issues are very related: the request form suddenly became very prevalent in the service agent's jira backend and how things are organised.