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

"Add flag" comment modal appears inconsistently depending on where "Add flag" is clicked.

      Issue Summary

      Our public docs state the following: 

      You can also add a comment when you're adding a flag to or removing a flag from an issue. You may want to do this to indicate your reason for adding or removing the flag.

      The comment modal only appears, however, when right-clicking an issue on the backlog and selecting "Add flag". If you go to an issue click the three dots [...] > Add flag no comment modal appears, the flag is simply added.

      Steps to Reproduce

      1. Go to the backlog of a company-managed software project
      2. Right-click on an issue and select Add flag
      3. Observe that a "Add flag and comment: 1 issue" modal opens:
      4. To see the different behaviour go to an issue and click the three dots [...] > Add flag. Observe that no modal appears, the flag is simply added.

      Expected Results

      Clicking "Add flag" should result in the same action regardless of where it is clicked.

      Actual Results

      Clicking "Add flag" by right-clicking an issue in a project's backlog opens a modal.

      Workaround

      n/a

            [JRACLOUD-87321] "Add flag" comment modal appears inconsistently depending on where "Add flag" is clicked.

            This bug is reproducible again. I have created a new one JSWCLOUD-27647

            Felipe Oliveira added a comment - This bug is reproducible again. I have created a new one JSWCLOUD-27647

            raymo added a comment -

            This should be fixed and consistent across all methods of adding flags in the Backlog. It should open a modal all the time.

            raymo added a comment - This should be fixed and consistent across all methods of adding flags in the Backlog. It should open a modal all the time.

            Any solution/update for this?

            Since it's quite helpful and important to provide context about why a Jira Issue has (or is now cleared of) an Impediment when its respective Flag is added (or removed), does anyone know if it is possible to use Automation or similar to require a comment be left when "Adding a Flag" or "Removing a Flag?"

            Nikhil Kundra added a comment - Any solution/update for this? Since it's quite helpful and important to provide context about why a Jira Issue has (or is now cleared of) an Impediment when its respective Flag is added (or removed), does anyone know if it is possible to use Automation or similar to require a comment be left when "Adding a Flag" or "Removing a Flag?"

            Reed, Dan added a comment - - edited

            Re: previous comment: It's a defect because the behaviour is inconsistent with no (obvious) reasoning behind it. Expected behaviour for many is that the modal will pop up regardless of where the flag is added. In reality the modal appears when you flag from some screen but not from others.

            Reed, Dan added a comment - - edited Re: previous comment: It's a defect because the behaviour is inconsistent with no (obvious) reasoning behind it. Expected behaviour for many is that the modal will pop up regardless of where the flag is added. In reality the modal appears when you flag from some screen but not from others.

            How is this a defect as the dialog to add the comment is the expected behavior?  Or, are there steps missing from the repro steps for this one for other configuration changes in the site?

            William Sheboy added a comment - How is this a defect as the dialog to add the comment is the expected behavior?  Or, are there steps missing from the repro steps for this one for other configuration changes in the site?

              Unassigned Unassigned
              23ef3e30d63c Anusha Rutnam
              Affected customers:
              22 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: