Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-12281

Closing an issue in a future sprint when jira.issue.editable is set to true won't remove it from the sprint and it leads to an error when a user tries to delete the future sprint

XMLWordPrintable

    • 6.07
    • 2
    • Severity 2 - Major
    • 0
    • Hide
      Atlassian Update – 23 October 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. Since the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will keep the issue open and continue to watch this issue for the further updates.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 23 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. Since the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will keep the issue open and continue to watch this issue for the further updates. Thank you, Ignat Alexeyenko Jira Bugmaster

      Reproduction:
      1. Create a new future sprint
      2. Create an issue and drag it into the future sprint
      3. Update workflow property of "Closed" status and set jira.issue.editable to true
      4. Close the issue.
      5. Update workflow property of "Closed" status and set jira.issue.editable to false
      6. Delete the future sprint
      Result : Error: This issue cannot be edited because of its workflow status.
      Expected: When closing the issue, it is removed from future sprint

        1. Screen Shot 2015-08-11 at 9.58.15 AM.png
          Screen Shot 2015-08-11 at 9.58.15 AM.png
          1.34 MB

            [JSWSERVER-12281] Closing an issue in a future sprint when jira.issue.editable is set to true won't remove it from the sprint and it leads to an error when a user tries to delete the future sprint

            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1

            Filipi Lima added a comment -

            For the record, the error when deleting the future sprint does not happen anymore. I've tested on 8.20.10 and 9.4.3 but it's been so long since this report that it might've been changed at any point.

            What does happen if you set jira.issue.editable and close the issue is that the Future Sprint will not be removed and if the Sprint is deleted there will not be any error but the issue will keep the customfieldvalue of that sprint even though there's no longer a reference on AO_60DB71_SPRINT table.

            Filipi Lima added a comment - For the record, the error when deleting the future sprint does not happen anymore. I've tested on 8.20.10 and 9.4.3 but it's been so long since this report that it might've been changed at any point. What does happen if you set jira.issue.editable and close the issue is that the Future Sprint will not be removed and if the Sprint is deleted there will not be any error but the issue will keep the customfieldvalue of that sprint even though there's no longer a reference on AO_60DB71_SPRINT table.
            SET Analytics Bot made changes -
            UIS Original: 3 New: 0
            SET Analytics Bot made changes -
            UIS New: 3
            Bugfix Automation Bot made changes -
            Minimum Version New: 6.07
            Ignat (Inactive) made changes -
            Status Original: Short Term Backlog [ 12074 ] New: Gathering Impact [ 12072 ]
            Ignat (Inactive) made changes -
            Current Status New: {panel:title=Atlassian Update – 23 October 2018|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. Since the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the [Atlassian Bugfix Policy|https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html] for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

            Atlassian will keep the issue open and continue to watch this issue for the further updates.

            Thank you,
            Ignat Alexeyenko
            Jira Bugmaster
            {panel}
            Labels Original: affects-server fixme saigon New: affects-server fixme low-interest saigon
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2853154 ] New: JAC Bug Workflow v3 [ 2936020 ]

              Unassigned Unassigned
              stang Son Tang (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated: