Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2016

Default Resolution causes issues to be committed with Resolution Date

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • None
    • 2.6.1, 2.12.1, 3.15.0
    • Usability

       Update 6 Aug 2020:

       This bug has been backported to Jira Core 8.5, will be available in the Jira 8.5.8 release.

       

       

        Update 17 Feb 2020:

      This bug is resolved by upgrading to Jira Core 8.8, relevant ticket: JRASERVER-70656

       

      Summary

      If we have default resolution set in JIRA, committing issues though live plans causes the new tickets created in the process to have a Resolution Date, though no Resolution.

      Steps to Reproduce

      1. Create a project
      2. Create a Portfolio plan and add the project as an issue source
      3. Go to Resolutions page in JIRA (type g+g >> resolutions, under https://instance.atlassian.net/secure/admin/ViewResolutions.jspa)
      4. Select a resolution as default
      5. Add an issue to the plan
      6. Commit it so it's created in JIRA

      Expected Results

      The ticket is created without Resolution Date, as it doesn't have a resolution.

      Actual Results

      It's created with no Resolution (as expected), but with a Resolution Date (not expected):

      Workarounds

      Workaround 1: no default resolution

      Don't make use of default resolution until you can upgrade to a fixed version.
      Clearing the default resolution on the Resolutions admin page's blocked by JRASERVER-70041, so to clear it you may:

      1. Create a new Resolution temporarily
      2. Set this new Resolution to be default
      3. Delete the new Resolution

      Workaround 2: tweak the workflows (suggested in comments below)

      1. Change the 'Create' transition for this issue
      2. Add a post-function to clear the 'resolution' (not resolution date)
        • This should also clean the resolution date

      Workaround 3: create issues in Jira

      1. Create issues directly through Jira, rather than Portfolio. This should avoid the problem.

        1. resolution_problem.png
          resolution_problem.png
          122 kB

              mliang@atlassian.com Mendel Liang
              jsilveira Jaime S
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: