Extend jira:uiModifications issue view support to Jira business (JWM) projects

Summary. jira:uiModifications supports the Global issue create view type on both Jira Software and Jira Work Management projects, but the Issue view and Issue transition view types are limited to Jira Software. I would like to ask for business (JWM) projects to be included in the issue view.

Why it matters for us. We run an ISO 9001 quality register in a company-managed business project: one issue = one corrective action, with custom fields for correction, root cause and corrective action (ISO 9001 clause 10.2.1) plus an external finding reference. Those fields only make sense for third-party and second-party audits; for internal audits they are noise on every form. A business project is the correct home for this work, since it is not software delivery, so moving it to a Jira Software project just to gain conditional field visibility would be the tail wagging the dog.

Current behaviour. With a UIM-based app (ScriptRunner Behaviours in our case), setVisible(false) correctly hides the fields in the Global Issue Create form, and has no effect on the issue view of the same project. I verified this with the condition replaced by a hardcoded false, so the modification itself is not reaching the view.

The practical consequence is an inconsistency that is confusing for end users rather than merely limiting: a field disappears while you create the issue and reappears the moment you open it.

Questions.

  1. Is issue view support for business projects on the roadmap, or is there a structural reason it is limited to Jira Software?
  2. Is there an existing ticket tracking this that I can follow or vote on? I could not find one.
  3. Is there any supported alternative for conditional field visibility on the issue view of a business project today?

Hi @GiovanniBorri,

That matches the docs. The manifest reference lists Issue view as Jira Software only, and Global issue create is the one view type that also covers Work Management. ECO-1664 asks for exactly this, still Gathering Interest with no fix version. Vote and watch it.

For today I’d check the Hide when empty divider in the field layout. Context fields dragged below it collapse into More fields when blank, and the audit-only ones are probably blank on internal audits anyway.

Right-hand context area only. Description-area fields stay put.

Separate issue types per audit kind is the static fallback. A jira:issuePanel only adds content, it can’t hide native fields.