Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-957

Forge workflow validator function does not receive configuration in payload during Jira issue transitions

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When using the jira:workflowValidator module in Forge, the configuration is available during editing and viewing through view.getContext().

      However, during a Jira issue transition, this configuration isn't available in the payload. Only basic issue and transition information is present but the validator configuration is missing.

      As a result, we must implement a workaround involving multiple steps to:

      • Decode the context token,
      • Extract the extension ID,
      • Use the Jira REST API to fetch workflows and match against project/extension ID,
      • Finally extract the validator config from there.

      This is seriously impacting our performance, increasing complexity and blocking our development.

      Could you please add the workflow validator configuration in the payload, mirroring the behavior of the Custom UI context?

       

       

            [ECO-957] Forge workflow validator function does not receive configuration in payload during Jira issue transitions

            Marek Szczepański [HeroCoders] added a comment -

            Hi cc8aaff0e17f 

            We tried to figure out a workaround, and it's not as easy as we thought initially.

            Could you please provide an official way to obtain the stored configuration during a Jira issue transition?

            We want to create a reliable solution for our customers and fulfil Atlassian's quality standards. 

            All Best

            Marek Szczepański
            Herocoders

            CC: klawal@atlassian.com 

            Marek Szczepański [HeroCoders] added a comment - Hi cc8aaff0e17f   We tried to figure out a workaround, and it's not as easy as we thought initially. Could you please provide an official way to  obtain the stored configuration during a Jira issue transition ? We want to create a reliable solution for our customers and fulfil Atlassian's quality standards.  All Best Marek Szczepański Herocoders CC: klawal@atlassian.com  

            Sven Paaß [Decadis AG] added a comment - - edited

            -

            Sven Paaß [Decadis AG] added a comment - - edited -

              2238f8e58844 Pratyush Kumar
              cc8aaff0e17f Leonardo Grzybowski
              Votes:
              23 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: