How can I avoid the end user adding the wrong approver?

Carson Sham July 17, 2024

 

How can I avoid the end user adding the wrong approver? for example, the wrong Top management staff are supposed not to approve that user.

1 answer

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 17, 2024

Hi @Carson Sham and welcome to the community!

Since you are on a premium plan, I would suggest to use Assets and prepopulate the approver field, based on the schema you create. E.g. you will create an Employee object type, which will take an attribute of type User named "Jira User" and another User Attribute called "Approver". Jira user will correspond to the actual jira user while on the approver you will set the default approver for each user.

Then add a post function (or an automation) to autopopulate the approver field based on the above schema.

Let me know if that helps! 

Carson Sham July 17, 2024

As we were using the Standard version before, can we have a short-term(Quick win) solution before we create an Employee object type?

Can we use Automation to handle this first?

Carson Sham July 30, 2024

@Alex Koxaras _Relational_ Can you please help to advise? Can we use Automation to handle this first? Many thanks.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events