In theory, yes. In reality, no.
Jira is not really backed by a database. It uses a database as a data store for convenience, avoiding writing its own data storage mechanisms and to take advantage of some database functions that aren't particularly data related.
To make it transactional, you'd need to add code to every place where Jira might write to its data store. That's a massive re-engineering project, and Atlassian sees that as pointless. (I don't, but I don't care about the cost or time, I just want more, better, functions. But I've got a massive list of those above making it transactional too)
What about this?
Are you sure that Jira isn't doing a transaction which can be rolled back by throwing an exception?
That's probably how validators work, no?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs