v0.1.0

Update version to 0.1.0, add data center compatibility

v0.0.6

Update version to v0.0.6

v0.0.5

Bug Fixes

• B: Freezing the history and manual changing of imported elements not working (CONCONDEC-32)
  • How can we store knowledge elements via the BandanaManager in Confluence to freeze them and to enable manual change?
    • rejected: We used to directly store knowledge element objects via the BandanaManager.
      • Recently, a class cast exception is thrown and this was not working anymore.
    • We use an ObjectMapper to serialize and deserialize knowledge elements before saving them via the BandanaManager!
      • Additional manual (de)serialization, which makes the code harder to understand
      • Manual (de)serialization works more reliable than directly storing knowledge element objects.

v0.0.4

Improvements

• WI: Show latest author of knowledge element instead of creator in stand-up table (CONCONDEC-31)
  • Which stakeholders should be shown in the stand-up table?
    • rejected: We show the creator of a knowledge element!
      • For decision knowledge elements in code comments, the creator of the code file might not be the one who wrote the comment.
    • We show the latest author of a knowledge element, i.e. the person who did the latest changes!

v0.0.3

Improvements

• WI: Update pom.xml and check plugin dependencies (CONCONDEC-18)
• WI: Highlight status of issues, decisions, and alternatives in the decision knowledge table (CONCONDEC-21)
  • Which text colors should the knowledge elements have regarding their status (for ambient feedback)?
    • Discarded alternatives and rejected decisions are colored in gray!
    • Unresolved issues and challenged decisions are colored in crimson red!
• WI: Change updatingDate attribute of KnowledgeElement class to latestUpdatingDate as passed via Jira ConDec's REST API (CONCONDEC-30)
• WI: Simplify possibility to manually import/edit JSON text (CONCONDEC-20)
• WI: Build and test Confluence ConDec plug-in via GitHub actions (CONCONDEC-28)
  • Which continuous integration server do we use?
    • Remove .travis.yml config, replace Travis CI with GitHub actions!
    • We now use GitHub actions as it is done in ConDec Jira!
      • Did not work with Eclipse ConDec, but is also succesfully used in Jira ConDec.
    • rejected: We currently use the Travis CI as the continuous integration server for the ConDec Eclipse plugin!
      • Does now only work with credits that we need to request via mail.
• WI: Show group-column in stand-up-table (CONCONDEC-25)
  • What diff coverage should be reached for unit tests of changed code in a branch/pull request?
    • Set expected diff coverage to 65%!
• WI: Enable to filter by start time, end time, knowledge type, and status (CONCONDEC-19)
  • Which filter possibilities should the meeting manager have for importing decision knowledge into Confluence?
    • The decision knowledge import macro offers the following filter criteria: project, search term, start and end time, decision knowledge type (issue, decision, argument, alternative), and decision problem status (resolved, unresolved)!
      • This is only a subset of the filter criteria available in Jira.
    • We could enable all filter criteria that are available in Jira, e.g. also documentation location.
      • Hard to implement in a Confluence macro.

v0.0.2

Improvements

• WI: Update REST API path to ConDec Jira plugin (CONCONDEC-16)
  • What path should the REST API have?
    • The path of the REST API for knowledge management is: Base URL/rest/condec/latest/knowledge/REST service!
      • This is the same path in all ConDec plugins.
• WI: Show more icons of knowledge elements in stand-up table (CONCONDEC-17)

v0.0.1

Improvements

• WI: Enable to configure macro parameters (CONCONDEC-14)
  • How can we configure the macro with "normal" macro parameters?
    • The name of the macro needs to be "decision-knowledge-import-macro" so that it can be configured!
• WI: Add Confluence macro that enables to import decision knowledge (CONCONDEC-2)
  • Should a manual import of decision knowledge (without an application link to Jira) be possible?
    • Enable the user to manually import decision knowledge into Confluence in a JSON format!
      • The manual import is something that the Jira import macro does not offer, it is one reason that shows that we need our own plug-in.
      • Is also working if there is no application link between Confluence and Jira.
• WI: Enable the user to get Jira issues directly from Confluence via Application Links (CONCONDEC-4)
• WI: Add decision knowledge icons and improve stand-up table (CONCONDEC-7)
• WI: Create JUnit tests for the Java code in the Confluence plugin (CONCONDEC-10)

Bug Fixes

• B: Fix macro ID bug (CONCONDEC-11)
  • How to enable multiple macros without saving the page first?
    • We retrieve the macro id from the Java Macro constructor to enable multiple macros!