What effects Jira when I delete a Portfolio Page?

[Stacy Finley]

I would like to delete a portfolio page that is old and not needed. Currently it is associated to a project within Jira that is currently using release and sprints. I've deleted a portfolio page before and it caused releases to disappear from issues in Jira and added a totally different release (just one example of the damage done). I have few more pages to delete and would like to do so without effecting what is already done in Jira.

Thanks!

[Earl McCutcheon]

Hi Stacy,

Deleting a portfolio plan should just delete the plan itself and not have any effect on the jira data directly.  The only thing I could think of of hand would be any uncommitted changes on the plan would be lost, but if a value has not been committed the value should not be present on the jira issue directly.

Look at the issue history of of an issue that you noted this behavior on and see if there is an entry at the time of the delete, or if the alternate fix version was entered at a separate time or by a different user, as there could have been a discrepancy in the rendered content in portfolio vs the values in the issue directly.

Also what version of jira/portfolio are you running, so I can do a quick test and see if there is a possible bug here, and are you able to reproduce this behavior in a test project/plan.

Regards,
Earl

[Stacy Finley]

Hi Earl,

We use the Jira Cloud version. Should be latest and greatest, right? I also realize that before I deleted the portfolio page, I excluded the releases even though they were active releases in Jira, I removed everything from scope, Removed the teams and disassociated the project with the team. Pretty much, I removed everything and then deleted the Portfolio project.

When I looked in the history of the issue, it shows that the fix/version was removed by me. Once I realized what happened, I created a new Portfolio page and then noticed that there was a big bundle of issues that show I removed one fix/version and added another fix/version. The same one for all of them which I did not do. 

So partially, I probably should not remove everything and just delete the project as is? But the second part is, if I delete and then make a new page for the same project, will it remove and re-add a new fix version?

I can attempt to try on a test instance I have as well.

Thank you for replying to my question!

Stacy

[Earl McCutcheon]

Hi Stacy,

Ahh yes, cloud missed that tag on the post, and yes cloud is going to be on the latest version.

I did a bit of playing around with this and I was not able to reproduce the data changes you note via resetting or changing any values on the plan that trigger changes in the issue data, so i'm missing something in the steps.  I tried various combinations of excluding issues and releases form the plan before deleting and recreating the plan, and all the data stayed static on the issues.

One thing you noted i'm not clear on is when you noted "I removed everything from scope", did you remove data from the fields in the scope or did you select the checkbox at the top of the scope section and exclude the issues from the plan to remove them from the scope?

Also at any point did you trigger a commit on the plan while removing and excluding the content?  As this is the only thing that I believe could have done this as the commit is doing a write event back to the Jira issue from the staged onscreen data in portfolio, and without a commit Portfolio should not write back to jira, so if you had removed a value in the scope from a version field either accidentally of in the clean up then committed, that change would be expected to update the field on the issue.

But ultimately deleting a Plan you should not need to make any changes to the issues in the plan up front, just deleting the plan and then create a new plan with the same content and Portfolio pulls field data from Jira into the new plan.  The content that is going to be touched would be the Plan specific content and settings such as Teams (that are not shared teams), Skills, Stages, configuration settings, etc..,  the Portfolio specific setting items would need to be reconfigured on the new plan after importing the data via the issue sources.

If you can test this in your test site please do so, and let me know what you find and if you can repro the data change as I want to make sure we do not have a Bug in the application.

Regards,
Earl