I’ve refreshed the workflow plugin a bit. If you want jump straight to the installation section.
A problem I’ve noticed with the workflows people create (not my own ones of course!) is that the resolution is often inconsistent.
This might stem from a lack of understanding of the resolution field and what it’s used for. In the default workflow, there is a state called Resolved, and when you get to that state the resolution must be set, and if you reopen the issue it’s unset, so people tend to think it happens by magic. It doesn’t, that’s the way the default workflow has been written, and there is no relationship between workflow states and the resolution, unless you define one. Continue reading ‘Jira Workflow Report Update’
This simple plugin allows you to run Groovy scripts in the context of confluence. Groovy scripts have full access to the API.
This is in the same spirit as the Jira groovy runner, that is, it lets you quickly develop proofs of concepts and simple macros, without having to worry about all the boilerplate of a Confluence plugin, and the agonisingly slow edit-debug-deploy cycle (even with JavaRebel). Developing should be as simple as adding your macro, saving the page, make changes to your groovy script, then reload the page.
If you use IDEA (probably true of Eclipse too) you can attach the debugger, and break in to your groovy scripts.
Example page output from running the three supplied scripts:
Continue reading ‘Confluence Groovy Runner’
