No. There's no way Jira can know what a post-function might do, so it can't roll-back anything.
If it’s not possible that’s one thing..but Jira is backed by a database...and databases can be transactional...so theoretically it should be possible without Jira knowing the details of the post functions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What about this?
https://docs.atlassian.com/jira/7.0.6/com/atlassian/jira/transaction/package-summary.html
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.