4. Update Commands for Causes
/qed addcause Command Details
Description: Adds a new cause or a sub-cause (at any depth) to the Investigation Map of the problem you are working on.
Input: /qed addcause
Output: You will see a drop-down selector to choose a path for the new cause you are adding, and you can specify the name of the new cause. If you choose the top-most value (problem number) then the cause will be added as a top-level cause for the current problem.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
/qed rmcause Command Details
Description: Deletes a cause or a sub-cause (at any depth) from the Investigation Map of the current problem.
Input: /qed rmcause
Output: You will see a drop-down selector to choose the cause you want to delete.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
/qed rename Command Details
Description: Renames a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed rename
Output: You will see a drop-down selector to choose the cause you want to rename, and you can specify a new name for that cause.
After you submit the command everyone in the channel will get a success message when the operation is completed.
Example:
/qed setstatus Command Details
Description: Sets the status of a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed setstatus
Output: You will see a drop-down selector to choose the cause and the status for the cause you selected to update.
After you submit your update everyone in the channel will get a success message when the operation is completed.
Example:
/qed assign Command Details
Description: Assign a user to investigate a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed assign
Output: You will see 2 drop-down selectors to choose the cause and the user (collaborator) you want to assign to investigate the cause you selected.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
/qed addnote Command Details
Description: Add a note to a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed addnote
Output: In the pop-up response, you will need to select a cause from a drop-down selector and you can add the note text.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
/qed rmnote Command Details
Description: Delete a note associated with a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed rmnote
Output: This command works in 2 steps:
- First, you will need to select a cause from a drop-down selector.
- Next, you will be able to select the note to be deleted.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
/qed addfile Command Details
Description: Attach a file to a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed addfile
Output: This command works in 2 steps:
- First, you have to upload your file to the Slack channel (use the clip icon at bottom right).
- Then you can type in this command and select a cause from a drop-down selector. This will cause the file you uploaded to Slack to be associated with the cause you selected.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
/qed rmfile Command Details
Description: Delete a file attached to a cause or a sub-cause (at any depth) in the Investigation Map of the current problem.
Input: /qed rmfile
Output: This command works in 2 steps:
- First, you will need to select a cause from a drop-down selector.
- Next, you will be able to select the file to be deleted.
After you submit your command everyone in the channel will get a success message when the operation is completed.
Example:
