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

Timer is not saved when you cancel activity and then undo the cancel #352

Closed
EsbenNedergaard opened this issue Mar 26, 2020 · 1 comment
Closed
Labels
Priority: medium Medium priority, it's neither high nor low priority Type: bug Bugs and other insects

Comments

@EsbenNedergaard
Copy link
Contributor

Describe the bug
When you add a timer to the activity and then cancel the activity imediatly after, however you regret that and undo the cancelation then the timer still seems to be there just fine, however if you leave the activity and go back into it your timer is now gone.

To Reproduce
Steps to reproduce the behavior:

  1. Go into any activity in the weekplan screen
  2. Click on the add timer button and add a new timer for an example for 5 seconds
  3. Click the "Aflys" button
  4. Click the "Fotryd" button
  5. Leave your activity
  6. Enter back into the activity, and see that your timer is now gone.

Expected behavior
I expected the timer to not get deleted when i undo my cancelling of an activity.

Actual behavior
The timer is some how deleted when you cancel then undo the cancelleation, the problem seems to be something with the undo button because if you cancel then undo an activity and then leave the activity you can sometimes for a short second see the red cross on the activity still.

@EsbenNedergaard EsbenNedergaard added the Type: bug Bugs and other insects label Mar 26, 2020
@EsbenNedergaard EsbenNedergaard added this to To do in 2020f 1. sprint via automation Mar 26, 2020
@Lortemanden Lortemanden added the Priority: medium Medium priority, it's neither high nor low priority label Apr 3, 2020
@MrPekar98 MrPekar98 added this to Issues to do in 2020f 2. sprint via automation Apr 9, 2020
@MrPekar98 MrPekar98 moved this from Issues to do to Issues in progress in 2020f 2. sprint Apr 9, 2020
@Lortemanden
Copy link
Contributor

Group 8 has worked with this in sprint 2.
They have looked at the problem but found the problem was in the web-api and made a issue in the api, but it might be a duplicate.
No group should be assigned to this issue since it will be solved by doing issue aau-giraf/web-api#98

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: medium Medium priority, it's neither high nor low priority Type: bug Bugs and other insects
Projects
No open projects
2020f 2. sprint
  
Issues in progress
Development

No branches or pull requests

4 participants