stijn-dejongh / trackmeup Goto Github PK

Right now only the Java component is covered in unit tests.
This should be extended into the javascript component to increase reliability, and maintainability.

Change the default ordering of the activities to a time-based order.
The first-order sorting should happen on deadline (if any) and on priority next.

The initial design is to provide several sorting-options, similar to the current filtering options.
Activities should be pulled in a sorted order when retrieved from the controller, making the client more light-weight. This responsibility assignment is prone to change if we notice slow performance due to request-latency later on.

Deadline does not reset properly, when leaving it blank the previous deadline is still selected

Implement subtasks and display of subtasks.

Change the functionality of the deadline warning colors in the overview to enable the user to set a notification timeframe.
If the delta between the current date and deadline falls within this timeframe, display the warning header color.

Increase the test coverage indicated by the Sonar Cloud analysis.
Target coverage is 70%, only non-trivial functions should be tested.
(no private constructor or getter tests).

Suggestion by Jasper vdb:

Add tooltips with summaries of button control effects to make the application more beginner-friendly.

Case:

• have an activity with subtasks.
• At least one subtask has a tag.
• Click the tag to filter it.

Result:
Subtask does not show up in filtered activities.

Expected result:
Subtask is included in the filtered activities, be it on its own, or within its parent.

Implement some sort of notes for activities.
This can be an optional functionality to be toggled by the user.
Notes should be saved in seperate files to not interfere with the TODO.txt-format of the activities.
Linking will be mono-directional: A note has a binding to activity, while activities are note agnostic.

Give users the option to upload a todo.txt file and use this as a basis to work from.

On branch refactor/mvp_pattern.

Issue when adding a graphic to the Done button in ActivityView.
When clicked and refreshed, the button text dissapears.
This issue does not occur when there is not graphic attached to the button.
Unit test indicates the text is there, but is simply not visible.
Bug only occurs on done button, edit/save and delete buttons are unaffected.

The desktop application does not refresh the activities from file when clicking the
'reload' button on the right in the activity overview.

Steps to reproduce:

• Set up a todo.txt file
• Create some activities through the UI
• Edit the todo file manually, and change an activity name
• Reload the activities from the UI
  =>Names in UI are unchanged and file (with changes) gets overwritten on edit.

Add a view to make kanban-style drag and drop possible.
Initial implementation with "TODO" -> "In progress" -> "Done" is sufficient for now.

Timetracking should not be linked to this status.

Add estimations (in hours) to activities.

Enable users to add an estimation to each activity. Add an overviewpage (or add this in the timesheet view) to show the difference between the estimated time, and the actual time.
The first implementation can be naive, future implementation might want to make note of higjh, middle and low estimations.
If possible add a way to display estimate accuracy over time, to see whether the actual time taken converges towards the estimate.

Implement prototypes for activities and subactivities that follow a standard format.
The goal is to select the prototype from a dropdown on activity creation and have the main activity along with the configured sub-activities created automatically.

Build in functionality to make activities editable.
Initial design is an edit-button that either makes the fields editable, or loads the activity in an editor.

Implement timesheet exporting to CSV file format for usage in workspace environments.
We still need to look into the proper formatting for this.
Suggestions are welcome.

Right now the name is not editable in the GUI because the open item is a flag based on the name of the activity. This should be changed to the imutable ID field.

When a name is edited, all subtasks are to be updated.

Per activity time tracking, and on demand time tracking display.