Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8218

Changing project default in project settings is not updating the project default value in automation rule.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Low Low
    • Automation
    • None

      Steps to reproduce:

      1. Go to project settings -> details -> set project lead and select project lead as default assignee.
      2. Navigate to the project > Project Settings > Automation -> Add rule -> Urgent issue alert
      3. Now click on the cog symbol on top of Urgent issue alert page to see the options. Under Run rule as it will show Project default and the name of project lead ion brackets.
      4. Go back to project settings again and change the project lead.
      5. Come back to automation rules, Urgent issue alert will still show the old project lead name under the run rule as option.

       

      Expected Behaviour:

      New project lead name should appear under the Run rule as option in Urgent issue alert automation rule.

       

        1. Screen Shot 2019-07-04 at 9.01.11 am.png
          Screen Shot 2019-07-04 at 9.01.11 am.png
          190 kB
        2. Urgent issue alert.png
          Urgent issue alert.png
          54 kB

            [JSDCLOUD-8218] Changing project default in project settings is not updating the project default value in automation rule.

            Vasilia Koulouri added a comment -

            Dears,

            As this is not a bug, what can we do to fix this issue as our customers also begin to notice this happening.

            Thank you in advance,

            Vasilia

            Vasilia Koulouri added a comment - Dears, As this is not a bug, what can we do to fix this issue as our customers also begin to notice this happening. Thank you in advance, Vasilia

            Michael Drew added a comment -

            Closing this as not a bug. This is more of a misunderstanding of what "Default user" refers to.

            The "Project default" for the "Run as user" setting at a per-automation-rule level does not refer to the project lead or the default assignee.
            The "Project default" for the "Run as user" setting at a per-automation-rule refers to the "Default run as user" setting for the project's automation rules (see the screenshot attached)

            For reference: https://support.atlassian.com/jira-service-desk-cloud/docs/advanced-automation-rule-options/

             

            Michael Drew added a comment - Closing this as not a bug. This is more of a misunderstanding of what "Default user" refers to. The "Project default" for the "Run as user" setting at a per-automation-rule level does not refer to the project lead or the default assignee. The "Project default" for the "Run as user" setting at a per-automation-rule refers to the "Default run as user" setting for the project's automation rules (see the screenshot attached) For reference:  https://support.atlassian.com/jira-service-desk-cloud/docs/advanced-automation-rule-options/  

            Rashi added a comment -

            This bug is raised via one of the users in community: https://community.atlassian.com/t5/Jira-Service-Desk-questions/Automation-Urgent-issue-alert-how-can-you-change-the-project/qaq-p/1093807?utm_source=atlcomm&utm_medium=email&utm_campaign=mentions_reply&utm_content=topic

            Rashi added a comment - This bug is raised via one of the users in community:  https://community.atlassian.com/t5/Jira-Service-Desk-questions/Automation-Urgent-issue-alert-how-can-you-change-the-project/qaq-p/1093807?utm_source=atlcomm&utm_medium=email&utm_campaign=mentions_reply&utm_content=topic

              Unassigned Unassigned
              ragarwal@atlassian.com Rashi
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: