• Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Normal Normal
    • Jira
    • None

      The Jira Github bot currently automatically sets tickets with merged pull requests to status "in development branch", but it does not set a "resolution". When closing a ticket which is "in development branch" Jira does not allow to set a resolution, which later makes Jira complain when doing a release.

      Can this be configured so the bot automatically sets "resolution: fixed" when changing to "in development branch"?

          [OTHER-352] Github Bot should set resolution

          yvanzo added a comment -

          It might be due to the “Close Issue” dialog being different in PICARD.

          Anyway, I fixed it by forcibly setting resolution to “Fixed” after transitioning status to “In Development Branch”.

          yvanzo added a comment - It might be due to the “Close Issue” dialog being different in PICARD. Anyway, I fixed it by forcibly setting resolution to “Fixed” after transitioning status to “In Development Branch”.

          Unfortunately this does not work, at least not for the PICARD tickets I just had the fresh PICARD-1744 changed status via Github workflow, but the resolution stayed on unresolved. I falled back to reopening the issue and closing it manually again. Any idea?

          Philipp Wolfer added a comment - Unfortunately this does not work, at least not for the PICARD tickets I just had the fresh PICARD-1744 changed status via Github workflow, but the resolution stayed on unresolved. I falled back to reopening the issue and closing it manually again. Any idea?

          yvanzo added a comment -

          Fixed automation rule to set resolution field to Fixed when transitioning tickets status to In Development Branch.

          yvanzo added a comment - Fixed automation rule to set resolution field to Fixed when transitioning tickets status to In Development Branch .

            yvanzo yvanzo
            outsidecontext Philipp Wolfer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package