Issue with assigning draft issuesDuring large document reviews, we often create a significant number of issues. A common workflow is to first create issues in Draft status and only move them to Open once the review has been completed or the information is sufficiently mature. In my case, I often fully populate a draft issue, including the description, proposed resolution, and assignee.However, the issue may still require additional input or verification before it is ready to become an active issue.The challenge is that once an assignee is selected, that person can already see and respond to the issue, even though it is still in Draft status. As a result, people sometimes start working on, commenting on, or responding to incomplete issues that are not yet ready for action. This often leads to unnecessary discussions, confusion, and noise in the review process. My suggestion would be that issues should only become 'assigned' to an individual once they are moved to Open status and are ready for action. Even when the assignee and followers are allready filled. Until then, draft issues should not trigger any notifications or actions for assignees. PS.I am aware that issues can be published and unpublished. However, in my view, this is not an ideal solution. Unpublishing effectively hides issues from the review process, which can create risks in terms of visibility and traceability. The core issue is not that draft issues should be hidden, but that they should not trigger actions or discussions before they are ready. I would therefore prefer a workflow where issues can remain visible in Draft status without being actively assigned until they are moved to Open.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Comprehensive Activity Tracking and Audit Trail for Review Workflows in ACC | 0 | 4.97 | 14-10-2026 |
| 2 | Issues Feature: Add the Ability to Edit Status Names and Colors | 0 | 4.44 | 13-10-2026 |
| 3 | Add Confirmation Prompt Before Assigning Forms and Issues | 0 | 5.18 | 12-08-2026 |
| 4 | Enhancement Request – Document-Wise Comment Export in a form of CRS template for Traceability | 0 | 6.46 | 14-10-2026 |
| 5 | Re: Integrate Legal “Stamp” with Review Status (Always Visible) | 7 | 7 | 17-07-2026 |
| 6 | Overview of my created issues on the start page (My Home) | 0 | 6.57 | 14-10-2026 |
| 7 | Search on task list | 0 | 5 | 11-07-2026 |
| 8 | Latency issues across a number of services | 0 | 12.62 | 23-07-2026 |
| 9 | PROEST - Workflow Roles | 0 | 4.05 | 13-10-2026 |
| 10 | Drag-Down Column Functionality in Plans Module List View | 0 | 6.38 | 12-08-2026 |