Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-88370

Cannot create issues when required fields are configured in workflow validator rather than field configuration

      NOTE: This bug report is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding bug report.

      Problem
      In case there are certain fields required for specific issue types and this requirement condition is modelled with a workflow validator, Advanced Roadmaps won't bring up the Create issue dialog when trying to commit an issue of this type to JIRA and hence the issue creation will fail.

      Steps to Reproduce

      Navigate to the workflow configuration page and select one to edit. 

      View the workflow digram and select the Create Issue transition. 

      Select the validators link and add a Field Required Validator

      **Publish the changes to the workflow

      Returning to the plan, create an issue applicable to this workflow

      Click on Review Changes, and then Save Selected Changes

      Result

      The workflow validation will be applied and the "Changes cannot be saved" notification is displayed to the user. 

      On the new improved interface:

      Could not be committed for unknown reasons.
      Item could not be committed for unknown reasons. Please contact your administrator.
      

      Workaround
      Configure the required field via field configurations and screens and specify the field behaviour this way.

      Notes
      The workaround doesn't apply to system fields that are locked by default (ie. Parent Link, Team)

      We are working on better supporting required fields via workflows.

            [JRACLOUD-88370] Cannot create issues when required fields are configured in workflow validator rather than field configuration

            I've attempted the workarounds, updates, and changes listed in the notes here, but I am still unable to create Epic-level items from ARM in a cloud environment. 

            Andrew Rezac added a comment - I've attempted the workarounds, updates, and changes listed in the notes here, but I am still unable to create Epic-level items from ARM in a cloud environment. 

            80947b53a166 ,
            Unfortunately I can't comment on when this will be ported to DC as that's handled by a separate team. I suggest that you follow and upvote this ticket for updates.

            Thanks

            Cam McKenzie added a comment - 80947b53a166 , Unfortunately I can't comment on when this will be ported to DC as that's handled by a separate team. I suggest that you follow and upvote this ticket for updates. Thanks

            Great news.
            Will this fix be ported to the on-premise versions of Jira?

            Roman.Benesch added a comment - Great news. Will this fix be ported to the on-premise versions of Jira?

            hey community,
            We have begun rolling out a fix for this issue today. It should be available on your Jira site within the next week or so.

            Customers with workflows that include validation steps can now create issues from their Advanced Roadmaps timeline.

            Previously, the issue creation function would fail if your workflow included validation steps. With this change, Advanced Roadmaps opens a modal allowing you to complete the required steps to create an issue from your timeline.

            Cam McKenzie added a comment - hey community, We have begun rolling out a fix for this issue today. It should be available on your Jira site within the next week or so. Customers with workflows that include validation steps can now create issues from their Advanced Roadmaps timeline. Previously, the issue creation function would fail if your workflow included validation steps. With this change, Advanced Roadmaps opens a modal allowing you to complete the required steps to create an issue from your timeline.

            We cannot create Epics from Roadmaps. I suspect it is because Epics require a summary and a description.
            (The behavior and error is as described above.)

            Roman.Benesch added a comment - We cannot create Epics from Roadmaps. I suspect it is because Epics require a summary and a description. (The behavior and error is as described above.)

            Hello together, I found a workaround to avoid the error "changes cannot be saved" 

            • Select "Teams" from the drop down menu, add your shared teams to the plan.
            • Select field and make the team option to be visible. Now create Epics or tasks and assign team directly within the plan.                                                            Now after saving the changes the error will no longer appear. I think this workaround is the only one for projects consist of multiple teams and use validator to make the team field as required.

            Sajin Antony added a comment - Hello together, I found a workaround to avoid the error "changes cannot be saved"  Select "Teams" from the drop down menu, add your shared teams to the plan. Select field and make the team option to be visible. Now create Epics or tasks and assign team directly within the plan.                                                            Now after saving the changes the error will no longer appear. I think this workaround is the only one for projects consist of multiple teams and use validator to make the team field as required.

            I encountered this issue on our Advanced Roadmap plan as well.

            Would love to see it fixed.

            Roger Mokarzel added a comment - I encountered this issue on our Advanced Roadmap plan as well. Would love to see it fixed.

            I tried the workaround to add the team field to a transition screen and added a Field Required Validator (JMWE app) validator for the Advanced Roadmap Team field.

            The regular Field Required Validator does not list the Advanced Road map Team field.

            and even though the value is entered pre-transition or on the transition screen, the validation fails to recognize that it is not empty. 

            Dorothy Krajewski added a comment - I tried the workaround to add the team field to a transition screen and added a Field Required Validator (JMWE app ) validator for the Advanced Roadmap Team field. The regular Field Required Validator does not list the Advanced Road map Team field. and even though the value is entered pre-transition or on the transition screen, the validation fails to recognize that it is not empty. 

            I encountered this issue on our Advanced Roadmap plan as well.

            Would love to see it fixed.

            Elad Israel Sadon added a comment - I encountered this issue on our Advanced Roadmap plan as well. Would love to see it fixed.

            To add fuel to this terrible fire, I've found that using the Field Required Validator on transitions has another nasty side effect - you can't create issues from Slack anymore. The Slack-Jira integration means that Slack only shows the fields that are required to be filled out via the required tag. Using this workaround to make fields required doesn't mark them as being required, thus the Create Issue screen in Slack does not show the fields that the validator will check - and now you cant fill them out and thus can't create issues from Slack.

            Anders Vagner Rostgaard added a comment - To add fuel to this terrible fire, I've found that using the  Field Required Validator on transitions has another nasty side effect - you can't create issues from Slack anymore. The Slack-Jira integration means that Slack only shows the fields that are required to be filled out via the required tag. Using this workaround to make fields required doesn't mark them as being required, thus the Create Issue screen in Slack does not show the fields that the validator will check - and now you cant fill them out and thus can't create issues from Slack.

              Unassigned Unassigned
              akavelar Albert Kavelar
              Affected customers:
              80 This affects my team
              Watchers:
              64 Start watching this issue

                Created:
                Updated:
                Resolved: