nofusscomputing / nofusscomputing/centurion_ui

Ticket Task Action Buttons

Open
#14 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type::feature
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 4h
Merged PRs (30d)
20

Description

When creating a ticket task (comment) the only way to change the comment from todo to done is to edit the comment and change the field from todo to done.

There should be a button for the tasks to mark as complete.

Additionally it would be good to see a start task and pause task button that would set the actual start time, pause and add time spent and then when the task is marked as resolved set the real end date and add any remaining time spent.


EoF Op


Task management is clunky as pointed out by OP. being able to have simple buttons for completing the task details, namely time tracking would be beneficial.

Details

Add to the header of a task comment the following icons that perform actions on the task in question:

  • Start task
  • Pause task
  • Mark as complete

These action buttons should be aligned right within the header of the task comment.

Currently the time tracking within a ticket is added to the ticket comment in question. However this will not work for the task action buttons as a user may take multiple iterations to complete a task.

Button Actions
  • Start Task: when clicked will set the real start date field

  • pause task: when clicked will measure the time from now to real start date and create an action comment under the task with user time spent.

    • Note: As it may take multiple iterations to complete the task this action must not set the tasks time spent field
  • mark as complete: when clicked will set the real finish date field and mark the task status field as done

Requirements

  • If responsible user field is not populated when start task button pressed, populate with user who clicked start task
  • If field responsible user is not set, no action button is to perform any action (disable buttons)
  • when start task button pressed and real start date field is populated the button is disabled
  • Clicking on pause task will not populate the tasks time field, it will create an action comment as a discussion under the task with the time spent.
  • When clicking pause task button, the real start date field is to be cleared.
  • Ensure the pause task action does not populate task time spent field
  • When task complete button pressed, for all action comments under the task that were used for tracking time are to be used to set the tasks real start date field.
  • Action comments used for time tracking each iteration must have the same fields as the task populated, minus the body.

Non-Functional Requirements

  • if reporting is done, it must not give impression of more tasks than were actually created
  • if reporting is done, when the time was spent, must be accurate
  • if reporting is done Tasks real start and finish dates must be from the start of the first timed to when the last timed was conducted

Tasks

  • Add Action button start
  • Add Action button pause
  • Add Action button completed
  • Documentation
  • Tests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by locating the task comment header and its existing time-tracking fields, then trace how task actions and comments are represented; done means the three requested actions, responsible-user rules, repeated time tracking, documentation, and tests satisfy the listed requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.