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

Leaving empty value for Tempo Account field configured as required doesn't show error

      Issue Summary

      If the Tempo Account field is defined as required for the Field Configuration (from the Tempo Account administration page) It works when creating an issue, but not working when editing the issue, (user is having the same screen for all Create, View, and Edit issue). It looks like the value was actually left in blank but after reopening the issue the value is still set (which is correct)

      Steps to Reproduce

      1. From Tempo Account administration page define the Account field as required
      2. Add the field to a screen
      3. Create an issue with a value for the field
      4. Edit the issue and leave the field empty, it will look like the value was removed instead of showing an error message indicating that the field is required
      5. Close and open the issue view and the value will reappear, look like the actually is never actually updated to remove the value as per the history, which is correct since the field cannot be empty

      Expected Results

      An error/warning would be displayed in the Edit issue screen as it does for the create issue screen (as per customer configuration it's using the same screen) 

      Actual Results

      No error is shown for the required field

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-76561] Leaving empty value for Tempo Account field configured as required doesn't show error

            Atlassian Update - May 4, 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 - May 4, 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
              4bd2fd3801db Jorge H
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: