Subtasks
closed
Lisa Schaar
closed
Samuel Lerch
Cameron Clancy Marco-Niklas Rathke: We talked about this suggestion internally and came up with the idea that we can already map subtasks in checklists via headings, so to speak: Create a headline, add individual tasks below the headline.
As soon as all tasks below this headline are checked off, the headline is also crossed out. In other words, it functions as a kind of superordinate task that is only completed once all subtasks have been checked off.
Now we are wondering if there are any other requirements for completing this request? Can you perhaps briefly give your assessment of this?
M
Marco-Niklas Rathke
Samuel Lerch: For me this sounds fine :)
Andreas Mauer
I have adjusted the title of this feature request and included the "follow-up tasks" topic as a standalone requirement. -> https://vote.seibert-media.net/checklists-for-atlassian/p/follow-ups-tasks
M
Marco-Niklas Rathke
"Should the checklist subtasks be able to be checked on/off " <- yes
Andreas Mauer
under review
Andreas Mauer
We would like to implement this feature but are unsure how to do it properly. So we would like to better understand who voted for what need.
When we talk about subtasks, do the voters mean..
- checklist subtasks, i.e. another hierarchy in checklists or
- Jira subtasks?
If 1:
Should the checklist subtasks be able to be checked on/off or is there simply a need to provide checklist tasks with more description in the form of text and e.g. lists?
If 2:
Should Jira subtasks then be created from checklists tasks, e.g. to further delegate a task that you can not complete yourself or where further action by other persons is necessary? Or is it just necessary to link Jira (sub)tasks to a checklist task?
Cameron Clancy
Andreas Mauer: The second image below with the blue checkmark is perfect for us. This enables us to block/group certain tasks for "if this applies" scenarios as well as visual structure (in some scenarios). Checking off subtasks is important.
Creating a Jira issue for the customers we currently have that want to use it would not be necessary, so lower priority for us.
However, if this was implemented, we might have use for this as here's a task we have on an existing checklist:
"Leave a COMMENT on this existing Jira issue (or raise a new Jira issue) to capture that this is failing or incorrect"
Cameron Clancy
Yes, we'd like indented sub-tasks also (but not follow-up tasks in Jira).
Here's an example:
- ...other tasks
- Turn on the overhead stage feedback monitor
- If the Mac ProPresenter computer isn’t running:
- Turn on the mains power source
- Turn on the Mac
- Log into the Mac as user 'Live Studio'
- Start up ProPresenter on the Mac
- Turn the Sony camera power on at the mains power source
- ...other tasks
The example above with indented items is only applicable if the Mac isn't already on.
Thanks for listening.
Samuel Lerch
Cameron Clancy: As I understand this requirement it is more about conditional checklist tasks.
Certain tasks are so-called "follow-up tasks" that only become relevant when a certain input or checklist task has been completed, right?
Accordingly, this could also be mapped via "Yes/No" queries in checklists, which then show a different checklist section depending on the given information.