Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time units accounted for wrong user because of multiple users working on drafts #3

Open
MarkusHlinka-OTOBO opened this issue May 16, 2024 · 0 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@MarkusHlinka-OTOBO
Copy link
Contributor

Scenario:

  1. User A creates a draft and records his time units spent.
  2. User B, who is for e.g. the supervisor of the ticket reviews the draft and sends it.

In this scenario the accounted time is accounted for User B, who sent the draft.

Wouldn't it be better, if the accounted time is saved for the user performing the action, as soon as the action is completed?
E.g.:

  1. User A creates a drag a records his time units spent.
    On draft save the spent time will be accounted for User A and the field for the accounted time is reset to 0.
  2. User B reviews and edits the draft.
    Since the accounted time is 0 again, the user is now able to just add his time spent on the ticket and as soon as he saves the draft again the spent time will be accounted for him and the field for the accounted time is reset to 0.
  3. User C finally reviews and sends the draft.
    Since the accounted time is 0 again, the user is now able to just add his time spent on the ticket.

If this would be possible the ticket would still have all recorded time units accounted and the recorded time would be separated to the right users.

@stefanhaerter stefanhaerter added question Further information is requested enhancement New feature or request labels Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants