didit - Checklists for Jira & Confluence

For compliance a audit log of when the templated it updated.

@mentions for headers to have specific users notified and reminders to send as well. Not sure if this would be done with metadata or not.

The metadata fields should be possible to put anywhere in the checklist and not just at the top.

We usually work with YES/NO tasks in our checklists. It would be helpful if, when a task is declared NO, there was an option to add a note or photo, as well as directly create a JIRA task.

We usually work with YES/NO tasks in our checklists. It would be great if we could immediately see how many NOs there are in a checklist. For example, there are already 50 checklists for a template. Analyzing each of these individually and identifying where a to-do is based on a NO is quite time-consuming. Perhaps the statistics function could be expanded to include these types of attributes.

It's impossible to print a Confluence page containing the didit macro once inserted into a document. The resulting document is completely broken and unreadable. In early versions, printing the page was feasible and functional.

Make recurring templates create Jira tickets with the template inside ready for actions rather than having to complete it outside of Jira.

Instead of an obscure domain a readable URI for the API would be better.

I have multiple staff working through a single checklist. Having this update in real-time without the need to refresh the page would make checklist so much more helpful.

It would be helpful for the visual structural presentation of a checklist if different heading levels (H1, H2, etc.) could be used. Related entries: https://vote.seibert-media.net/checklists-for-atlassian/p/ways-to-improve-structure-of-very-long-checklists https://vote.seibert-media.net/checklists-for-atlassian/p/add-bold-underline-and-italic-options-for