Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to rollback changes in Portfolio after reconfiguration

I was reconfiguring Portfolio, but when all versions were selected I clicked remove selection for all and added only few that I needed to add. But "Remove selected" actually removed ALL selected even the old ones that were already there. 

In this case Portfolio doesn't require the Committing of changes, so is there a way to restore data that was before?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 21, 2018

Hi @Dmitry Karasev,


I'm assuming here that this happened during a Portfolio Plan creation, in which case once the plan is created you can go in the plan configuration and edit the issue source. This will let you go through the creation steps again so that you can include everything you need (Documentation).


Hope that helps!




No it happened when I reconfigured Portfolio plan to add new Epics. Thats why when I clicked remove selected - all versions were removed even those that were selected before. Yes it's probably expected, but problem is - reconfiguration does not require to Commit changes, so when I realized that I removed some versions, it was too late

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 22, 2018

Going through the issue source configuration does not require to commit changes indeed because it does not change any data in Jira. Everything done during that process should be reversible by simply going through the configuration again.

On a related note, deleting releases that were created in Portfolio but not committed (e.g. Release never existed in Jira) does not create an uncommitted changes.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events