nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deleted Balsamiq Mockups project by mistake

Paul Alexander

I have a user who had a large Balsamiq Mockup project embedded on a Jira issue. We have both the balsamiq for jira and balsamiq for confluence products. He deleted the .pmpr attachment on the jira issue thinking it was junk and now discovered that his balsamiq mockups project is deleted. If it was in confluence I could probably retrieve it from the space's trash can but I know of no means to get this back from a jira ticket.

I do not have the original bmpr file anywhere.

Could atlassian support help or am I out of luck?

Accepted answers

Mohamed Benziane

Hello,

You have to ask the atlassian team if they have a backup. But when someone delete something in jira is gone forever.

Ask your admin if isn't you to allow only some users to delete attachment.

Hooe this helps.

All comments

Mohamed Benziane

Hello,

You have to ask the atlassian team if they have a backup. But when someone delete something in jira is gone forever.

Ask your admin if isn't you to allow only some users to delete attachment.

Hooe this helps.

Paul Alexander

I posted an atlassian ticket just in case they could help.

I allow deleting an attachment that you own. If I take this away, no one can delete anything. I will educate folks not to do this. I think Balsamiq should simply not allow this or somehow hide the bpmr file from the list.

Brendan Saricks

Unfortunately, I believe only Jira Admins can show or hide attachments, Paul. We cannot affect that from the app's side.

I'm sorry for the trouble you and your team are having here. I wish there was more we could do to help.

Paul Alexander

It seems users don't realize that the bmpr file represents the balsamiq mockup project. While there is a 'delete project' function in the balsamiq region of the jira issue, the file itself under the attachments section could look like garbage to someone trying to tidy up a jira issue. Nonetheless, this is a training thing. I'll explain to our supers and leads to educate their folks.

An option could be revoking 'delete attachment' permissions in my schemes but that would not make most people happy since they'd need to escalate to someone (probably a small handful of people) to remove things when requested. But, yes, this would preserve mishandling of this very important file. Thx all.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

balsamiq