The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • The Forge app is unable to enforce the non-editable behavior for custom fields in Jira's List View.

The Forge app is unable to enforce the non-editable behavior for custom fields in Jira's List View.

hoongchun.lim
July 29, 2025

Hi, I'm not sure if this is a bug, but I applied a restriction to make a custom field non-editable in the Jira Issue View. However, I recently discovered that this functionality only works in the Jira Detail View and does not apply to the Jira List View. It seems that this happens because the Jira Detail View operates as an object, which triggers the Forge UIM, while the Jira List View functions as an array and does not recognize the specific ticket being referenced. Has anyone encountered this issue before? If so, do you have any suggestions or workarounds?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Marc -Devoteam-
Community Champion
July 29, 2025

HI @hoongchun.lim 

Best is to ask this question in the Atlassian Developer Community

Or reach out to Atlassian Support

hoongchun.lim
July 29, 2025

Hi @Marc -Devoteam- , yup

I have raise ticket to Atlassian Support

Like Marc -Devoteam- likes this
hoongchun.lim
September 26, 2025

Sorry for the delayed update. Here’s the Ecosystem ticket they created: ECO-1002. There haven’t been any new responses for about a month.


DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events