The ConDec Confluence plugin enables to integrate decision knowledge into meeting agendas. It enables the meeting creator to filter for decision knowledge to be shown in the meeting agenda. For example, it enables the meeting creator to filter for decision knowledge created and relevant for the last sprint. Thus, the developers get an overview which issues (decision problems) need to be solved or were solved, i.e., which decisions were made during the last sprint or need to be made during the upcoming sprint.
The following prerequisites are necessary to compile the plug-in from source code:
- Java 11 JDK
- Atlassian SDK
The source code is compiled via terminal. Navigate into the cures-condec-confluence folder and run the following command:
atlas-mvn package
The .jar file is created.
Run the plug-in locally via:
atlas-run
The precompiled .jar-File for the latest release can be found here: https://github.com/cures-hub/cures-condec-confluence/releases/latest
To share decision knowledge between Jira and Confluence, they need to be linked via an application link. The authentication type needs to be OAuth (impersonation).
The Decision Knowledge Import Macro can be used to create a stand-up table in meetings.
Macro to import decision knowledge from Jira
The stand-up table lists open and solved decision problems, decisions, and other decision knowledge elements for a certain time frame. The list of decision knowledge elements supports the developers in discussing recently made decisions and open decision problems during meetings.
List of decision knowledge elements as part of a meeting agenda/protocol (used as stand-up table)
ConDec's decision knowledge import macro is different to the Jira issue import macro in the following ways:
- It imports decision knowledge documented in various documentation locations, in particular, Jira issue description and comments, code comments, commit messages, and entire Jira issues. The Jira issue import macro would only enable to import decision knowledge elements documented as entire Jira issues.
- It enables to freeze the imported elements so that changes made in the decision knowledge documentation after the meeting are not shown in the meeting protocol of a former meeting. That means that ConDec's decision knowledge import macro enables to preserve the history.
- It enables to manually input a JSON String exported from Jira, e.g. if there are no application links, and to manually edit the JSON String.
- The unresolved decision problems (issues) are highlighted using red text color to nudge the developers to collaboratively make and document a decision.
Configuration possibilities for the decision knowledge import macro when editing a Confluence page. The macro enables to manually edit the imported knowledge elements.
Dialog to manually paste a JSON String exported from Jira or to manually edit the imported knowledge elements.
The decision knowledge is imported from ConDec Jira via the REST API. To access ConDec Jira's REST API, the application link between Confluence and Jira is used in the JiraClient class.