We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-663

Change the message error "Inactive user" in the Audit Logs to be more accurate

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      At the moment, the lookup of a user picker field is by ID and not text, so when a rule tries to populate the field A4J shows a message saying "Inactive user" even if the user is active:

      And as for the logs, the message we receive is:

      Response body: {"errorMessages":["Specified user does not exist or you do not have required permissions"],"errors":{}}

       
      That said, changing the message error in the Audit Logs to be more accurate such as "You can only populate a user picker field by ID".

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Automation for Cloud'
            1. Automation for Cloud
            2. AUTO-663

            Change the message error "Inactive user" in the Audit Logs to be more accurate

              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                At the moment, the lookup of a user picker field is by ID and not text, so when a rule tries to populate the field A4J shows a message saying "Inactive user" even if the user is active:

                And as for the logs, the message we receive is:

                Response body: {"errorMessages":["Specified user does not exist or you do not have required permissions"],"errors":{}}

                 
                That said, changing the message error in the Audit Logs to be more accurate such as "You can only populate a user picker field by ID".

                        b5485955f50a Michael Fedulov
                        360fcb72514e Josiane Oliveira (Inactive)
                        Votes:
                        3 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            b5485955f50a Michael Fedulov
                            360fcb72514e Josiane Oliveira (Inactive)
                            Votes:
                            3 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: