Changing status, priority and due date
One dialog carries status, priority, privacy and dates, so a single pass keeps a record honest.
- Open the issue, feature request, change request or task. On a narrow screen, tap Details & actions first.
- Click Actions, then Change Status.
- Pick from Select Status. Issues, feature and change requests and tasks share the same seven states:
open,in-progress,pending-review,need-meeting,rejected,cancelledandclosed. The dialog itself offers six of them;cancelledis reachable by dragging a task into the Cancelled column on the Task Tracker board. - Pick from Select Priority. There are four levels:
low,medium,highandurgent. The task and subtask create dialogs offer High, Medium and Low only. - Pick from Select Privacy Type, either External or Internal. See the privacy topic below before you change this on a live record.
- Set the Due Date, or, if you chose a closing status, fill in Closing Date (Required) and Closing Reason (Required). Those two replace the due date field, because a finished record is dated by when it finished.
- Click Change Status. A confirmation toast appears and the panel updates in place.
closed, rejected and cancelled are the terminal three. The dialog warns that closing or rejecting is meant to be final, and if you do move an already closed item somewhere else it asks you to confirm the reopen first. Delete Request is disabled while an item is closed. Comments stay open for seven days after the closing date and are then locked, with the input replaced by a line saying so.
need-meeting and pending-review exist because work stalls for honest reasons. A record waiting on a conversation is not the same as a record nobody has started.
If the project is connected to a GitHub repository, moving an item into closed, rejected or cancelled closes the mirrored GitHub issue, and moving it back to any other status reopens it. The connection itself is set up in the admin panel, not here.
A client request is different: before it is sorted it carries its own four states, unsorted, sorted-issue, sorted-feature and sorted-change, and it only reaches the seven above once you have sorted it.
See this on your own workflow
This is the product as it stands today. A call is where you find out which parts of it your team would turn on, and what a deployment looks like.
partnerships@dhcertainty.com