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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Adding Jira Align users to Portfolios vs Programs

When you add users to Jira Align, do you just add them to the portfolio and then copy them to the program?  This article may make you think twice about that.

 

Did you know that not adding users to programs can restrict some unwanted behavior without controlling it via the system role? 

There may be instances where companies want to create hybrid roles because there may be some shared responsibility in data entry in the tool.  For example, some companies may want to give both their Product Managers and their Product Owners the capability to enter features.  However, they may want to restrict the ranking/prioritizing of the backlog only to the Product Manager.

Adding the a user to only the portfolio and not the program, restricts their ability to rank the backlog.  In addition to the example provided above, following this practice can also reduce the common mistake of users sorting by a column in the backlog and accidentally applying rank to the the column that was sorted.

Another restriction imposed is on the Program Board.  Only users that are added to a Program are able to move features on a Program Board.

As you can see, limiting the addition of users to the portfolio has its benefits.  When a user is added to the portfolio and not the program, they can still see all of the work within that portfolio and any programs and teams below it.

Now in cases where a company may want to restrict users to only see work associated with their program, adding a user to only the program would be the optimal choice.  In this instance, they can still see themes and epics that are tied to their program, just not everyone else's.

So taking a moment to think about this and putting this as an option to determine the best approach may be worth it.

2 comments

Thanks Rae,  do you know if it is in the Jira Align roadmap to add issue security similar to what Jira offers now?

Rae Gibbs Atlassian Team Jan 13, 2020

Sorry, I don't know the answer to that one. 

Like Allan Maxwell likes this

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Align

Helpful hints if you're rolling Align out to your entire enterprise

(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...

1,110 views 3 25
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