Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-835

better resolution for duplicate issues

    XMLWordPrintable

    Details

    • Team:
      SQuaRE

      Description

      We should be able to resolve issues as duplicates, not just link them. Should probably have similar resolutions for "invalid", "wontfix", "obsoleted [by]", maybe others.

        Attachments

          Activity

          Hide
          gpdf Gregory Dubois-Felsmann added a comment -

          It was suggested just now that I create a ticket on this topic. I found this existing one instead, and have raised its priority and reassigned it to Frossie.

          The request is to provide some way to show a ticket as closed because it duplicates another (open) issue.

          The alternatives are to have a "duplicate" Status that rolls up to an interpretation as "closed" for accounting purposes, or to use the "done" Status with a Resolution of "duplicate". Similar issues apply for outcomes like "WontFix" as mentioned by Jim.

          Frossie's proposal is to do the former - i.e., have a "duplicate" value for Status.

          Show
          gpdf Gregory Dubois-Felsmann added a comment - It was suggested just now that I create a ticket on this topic. I found this existing one instead, and have raised its priority and reassigned it to Frossie. The request is to provide some way to show a ticket as closed because it duplicates another (open) issue. The alternatives are to have a "duplicate" Status that rolls up to an interpretation as "closed" for accounting purposes, or to use the "done" Status with a Resolution of "duplicate". Similar issues apply for outcomes like "WontFix" as mentioned by Jim. Frossie's proposal is to do the former - i.e., have a "duplicate" value for Status.
          Hide
          gpdf Gregory Dubois-Felsmann added a comment -

          Note that this request really should apply across the LSST JIRA projects, subject to the agreement of their administrators.

          Show
          gpdf Gregory Dubois-Felsmann added a comment - Note that this request really should apply across the LSST JIRA projects, subject to the agreement of their administrators.
          Hide
          swinbank John Swinbank added a comment -

          While I don't disagree with this request, we've now processed nearly ten thousand tickets without this workflow and our current system (as described at https://developer.lsst.io/processes/workflow.html#ticket-status) seems to be working ok. Can we just "won't fix" this one?

          Show
          swinbank John Swinbank added a comment - While I don't disagree with this request, we've now processed nearly ten thousand tickets without this workflow and our current system (as described at https://developer.lsst.io/processes/workflow.html#ticket-status ) seems to be working ok. Can we just "won't fix" this one?
          Hide
          tjenness Tim Jenness added a comment -

          I also agree that using INVALID status for duplicate tickets is a bit weird and that DUPLICATE would be better but I'm happy to let this slide at this point.

          Show
          tjenness Tim Jenness added a comment - I also agree that using INVALID status for duplicate tickets is a bit weird and that DUPLICATE would be better but I'm happy to let this slide at this point.
          Hide
          gpdf Gregory Dubois-Felsmann added a comment -

          I like the Resolution=Duplicate approach, but I agree with the above comments that this is not worth fiddling with at this point.

          Show
          gpdf Gregory Dubois-Felsmann added a comment - I like the Resolution=Duplicate approach, but I agree with the above comments that this is not worth fiddling with at this point.
          Hide
          jbosch Jim Bosch added a comment -

          As the original reporter, I have no objection to living with what we have.

          Show
          jbosch Jim Bosch added a comment - As the original reporter, I have no objection to living with what we have.

            People

            Assignee:
            frossie Frossie Economou
            Reporter:
            jbosch Jim Bosch
            Watchers:
            Gregory Dubois-Felsmann, Jim Bosch, John Swinbank, Tim Jenness
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: