Comments and tags on reconciliation exclusion
planned
R
Rick van den Dijssel
Goal: Improve traceability and filtering when excluding issues from reconciliation by allowing users to specify reasons and categorize exclusions with tags.
- Add Comment Field on Exclusion
- When excluding an issue, users should be able to enter a free-text comment.
- Purpose: To describe the reason for exclusion (e.g., link to a ticket, explanation, etc.).
- The comment should be visible in the issue details and available for future reference.
- HTML santization.
- Add Multi-Select Tag Field on Exclusion
- Allow users to assign one or more tags when excluding an issue.
- Tags should be user-defined, similar to tagging in Azure DevOps.
- System should provide autocomplete/suggestions from previously used tags.
- HTML santization.
- Bulk Mode Behavior
- When excluding multiple issues in bulk:
- A single comment and tag set should apply to all selected exclusions.
- Users should enter the comment and select tags once for all.
- Filter on comment and tag field
- Allow user to filter on the comment (contains) and tag (equals one of the items) in the excluded list view
- System should provide autocomplete/suggestions for tag in the equals condition
- Add support for empty filter on tags
- Elastic audit logging
- Add comment and tags to the existing audit logging to elastic
Use Case Example
A user excludes an account and enters the comment:
- Linked to ticket TICKET-1234 – account under review
- They select tags: ["admin account"]
- This enables others to:
- See why it was excluded
- Filter for all exclusions with the tag "admin account"
- Revisit later once the ticket is resolved
Limits
- Max number of tags in tag field is 10
- Limit max number of unique tags to 1000
- Max limit of tag length (same as br category)
- Max lenght of comment is 1024
R
Rick van den Dijssel
Merged in a post:
Add comment field to reconciliation actions
R
Ron Kuper
When I am performing an action via the reconciliation report, I would like to be able to add a comment or reference. This is to 'link' the action or bulk actions to (for instance) a TOPdesk ticket or meeting notes where the actions are approved or requested. This is for audit trail purposes and should also show in the elastic reports so this can be exported.
R
Rick van den Dijssel
planned
Planned October release
R
Rick van den Dijssel
Thank you for posting, Ron Kuper! I have a few more questions for you:
- What specific information would you like to include in the comment field for reconciliation actions?
- How frequently do you anticipate using the comment field for reconciliation actions?
- Are there any specific formats or templates you would prefer for the comments in the reconciliation actions?
R
Ron Kuper
Rick van den Dijssel
- ticket references or references to meeting notes.
- for almost all actions performed
- should be for short comments, not long lines of text