Post function "Set field value - Issue Type" should fail if the issue types do not share the same workflow

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Low
    • Component/s: Ecosystem
    • None
    • 2
    • Severity 3 - Minor

      Summary

      The issue does not show the transitions associated with the issue type.
      Using the post function Set field value (JMWE add-on) to change the issue type of a JIRA issue to an issue type that does not use the same workflow, causes the issue to be bugged with wrong transitions.

      Environment

      JIRA Cloud

      Steps to Reproduce

      1. Create a project
      2. Create a workflow (e.g Workflow 1)
      3. Assign an issue type to this workflow (e.g Issue type 1)
      4. Create a second workflow (e.g Workflow 2)
      5. Assign another issue type to this second workflow (e.g Issue type 2)
      6. In a transition in the Workflow 1, create a post function Set field value (JMWE add-on) and in the Field select Issue type. In the Value, select the issue type Issue type 2 of the Workflow 2.

      Create a test issue and transition the post function you created.
      The issue will change its issue type (to Issue type 2), however, it will be stuck in the same workflow (Workflow 1), causing the issue to be in a "bugged status".

      Expected Results

      • It should Fail if the issue type is not in the same workflow.

      Notes

      Use this query to check the workflow the issue is currently in

      select * from os_wfentry where id = (select workflow_id from jiraissue where issuenum = 1234 and project = (select id from project where pkey = 'ABC'));

      Workaround

      In order to update the issue type value of a JIRA Ticket to a type that does not use the same workflow, the issue must be moved instead.

              Assignee:
              Unassigned
              Reporter:
              Gabriel Muller (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: