Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-563

Automation is failing to set priority when priority is NULL on issues

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 8.0.5
    • Actions
    • Severity 3 - Minor
    • 1

      Issue Summary

      Whenever we attempt to generate and run automation to edit the priority field and if this field is NULL, automation is ignoring the field and not setting it.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      • Update the priority field of any issue to NULL in DB
        update jiraissue 
        set priority = null 
        where id = <MY_ISSUE_ID>;
        
      • Create a simple automation:
        • Trigger: When: Issue commented
        • Action: Edit field - Priority, then select the desired priority
        • Visit the issue where you updated the priority in step 1 in DB and then place a comment.

      Expected Results

      As a Jira admin I expect the automation to set the priority without failing or generating errors

      Actual Results

      Workaround

      Based on some business needs may not be possible to update the priority field in jiraissue table in DB before running the automation, hence there is no useful workaround at moment, but even so sharing this possibility here.

      • Perform the select below to raise an existing priority:
        select id, pname from priority p ;
        
      • Once the id was raised, then update the jiraissue table to set the priority
        update jiraissue 
        set priority = <MY_PRIORITY_ID>
        where id = <MY_ISSUE_ID>;
        
      • Rerun the automation

              Unassigned Unassigned
              a043f042db56 Jose Filho
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: