Unassigned backlog logic fails due to invalid issue type

XMLWordPrintable

      Issue Summary

      If there is an invalid issue type configured and even if none of the work items of the invalid type sync with Jira Align, unassigned backlog logic does not work as the Jira API returns 400 for JQL query.

      This is reproducible on Data Center: NA

      Steps to Reproduce

      1. Configure a bad issue ID such as defect=99999
      2. Complete a sprint on Jira and move pending items to backlog
      3. Observe the pending items are not moved to unassigned backlog on Jira Align

      Expected Results

      1. Even if there is a bad issue type configured, unassigned backlog logic should work

      Actual Results

      1. If there is a bad issue type configured, unassigned backlog logic fails

      The below exception is thrown in the Connector.log file:

      Jira API Response: 400 bad request 
      

      Workaround

      Correct the issue type fields

            Assignee:
            Yannick Genin
            Reporter:
            Manideep Neeli
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: