Balsamiq 3 Download

0 views

Skip to first unread message

Nella Mcnairy

unread,

Aug 3, 2024, 4:31:28 PM8/3/24

to ocpindiscwee

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 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.

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.