Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Comala - Select a specific User/Group for next state with restrictions

Hi Guys, here is first the Use Case:

State is Draft - a user or group (A1) has set restrictions for view and edit.

Now the User from A1 want send this state to another (state VIEW).

Before the status changes, the user A1 should be asked who should be added as user/group in the next status.

The new/new user/group A2 must also have restrictions in the next status, because nobody except user/group A1 and A2 should see and edit the document.

How can i do that?

1 answer

1 accepted

Hi Kay,

You could create a new user type parameter P1 and configure the next state to require it.

This functionality is called required params, you can find more information here.

Then, you could add P1 value to the page edit restrictions. Please find below a markup example about what you are trying to implement:

{workflow:name=Testing required params}
The Publishing Workflow has four states.
Ready: Edited by Staff. Reviewed: Reviewed by Managers. Published: Approved by Editor-in-Chief & viewable publicly.
You can define the Reviewer and Editor-in-Chief in the Space Admin Workflow Configuration.
{workflowparameter:Reviewers Group|description=Please add the reviewers group|type=group|edit=true}
{workflowparameter:Reviewers Users|description=Please add the users|type=user|edit=true}
{workflowparameter:Reviewers|description=Please add the users group|type=user|edit=true}
{state:Ready|approved=Reviewed|rejected=Draft|requiredparams=Reviewers Group,Reviewers Users}
{approval:Final approval|final=true|assignable=true}
{add-restriction:type=view|group=@Reviewers Group@|user=@Reviewers Users@}
{add-restriction:type=edit|group=@Reviewers Group@|user=@Reviewers Users@}

I hope that helps,

Thank you for the hint. Problem is, that we don´t work with the standard groupnames. And we have here a second problem, i can´t choice a user or a group, i must take user and group or i received an error axception, cause the expected field has no value. 

It´s okay, so we can choice a group or a user (but not as required) and that works for us.

Thank you!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New cloud apps roundup - June 2021

Since our last roundup in April, Atlassian's Marketplace Partners have added over 100 new cloud apps to the Atlassian Marketplace to help your teams work more efficiently. Let’s take a quick look a...

377 views 5 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you