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

Issue collector edition fails silently when "Allow unassigned issues" is turned off

      Issue Summary

      You cannot create or edit issue collectors if the option Allow unassigned issues is set to OFF in the general settings. That happens because the Assignee field is set as required by default, but it cannot be used in the issue collector.

      The problem is that when you have that option disabled, and you try to perform one the mentioned actions with an issue collector, no error message will be displayed. The issue collector will just not be updated.

      Steps to Reproduce

      • Turn the option Allow unassigned issues off in the general settings: https://<INSTANCE NAME>.atlassian.net/secure/admin/EditApplicationProperties!default.jspa
      • Attempt to edit an existing issue collector;
        • E.g. try to add a custom field to its form.

      Here's a recording showing the behaviour: Issue collector edition fail.mp4

      Expected Results

      An error message will be displayed, stating the reason why the issue collector was not updated.

      Actual Results

      The issue collector just won't be updated, and no error message will be displayed.

      Workaround

      None at the moment.

            [JRACLOUD-75743] Issue collector edition fails silently when "Allow unassigned issues" is turned off

            Atlassian Update - July 5, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - July 5, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              lalmeida@atlassian.com Leonardo De Almeida
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: