You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
You can install Portfolio in your current production it will pull data from your Jira and is basically a layer that sits on top of your projects to show you the high level project plan.
However, if you don't want it affecting the projects, you should never commit the uncommitted change back to your Jira (this is a button in the plan that will ask you to review and commit the changes once you're happy with it)
Clicking that button will take you to a screen to review and commit changes, so if you don't want to do any changes back to production you should not click on this. Uninstalling portfolio will have no affect on your projects as long as you don't commit changes.
You would also need to restrict the permission to Portfolio as well if you don't want users to start creating plans etc and committing back to Jira, but it can only be restricted by Groups so if its something for you to test yourself you will need to create a group just with you in it.
I would suggest to create a new user just for Portfolio testing, create a group "portfolio test" and add your new user to it. The group should only have browse project permission (with no issue permissions this will stop any accidental commits back to Jira), give this group access to Portfolio in JIRA Administration -> Add on -> Manage add on -> Portfolio permission and remove all other groups.
You can then log in as this user, and create your portfolio plan for the project in question and experiment with it.
Although I would suggest to create a test environment with your production data, so you can experiment with Jira Portfolio in full instead without fear of affecting your production!
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.