You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I click the plus button, it shows a closed section. I think it would be more clear and user friendly if it's opened when you click "+"
Also are the arrows mixed up? I'm used to pointing down means expand, and pointing up means close
To Reproduce Bug
Steps to reproduce the bug:
press the + button
Expected behavior
Maybe it should be opened after you add the section
Screenshots
It's closed after "Adding" by default
Additional context
Add any other context about the problem here.
--------------- End of User Report: DO NOT MODIFY ITEMS BELOW THIS LINE ---------------
GitHub Issue No. / ID
Team Task
Here will be added Team declaration by Team Leads.
Development start date
Date when dev team start fixing a bug
Development end date
Date when dev team complete fixing a bug
BugFix Deploy Date
Date when BugFix is deployed, and Bug Issue is closed
PO Comment
Here will be PO team add a comment.
The text was updated successfully, but these errors were encountered:
Describe the bug
When I click the plus button, it shows a closed section. I think it would be more clear and user friendly if it's opened when you click "+"
Also are the arrows mixed up? I'm used to pointing down means expand, and pointing up means close
To Reproduce Bug
Steps to reproduce the bug:
Expected behavior
Maybe it should be opened after you add the section
Screenshots
It's closed after "Adding" by default
Additional context
Add any other context about the problem here.
--------------- End of User Report: DO NOT MODIFY ITEMS BELOW THIS LINE ---------------
GitHub Issue No. / ID
Team Task
Here will be added Team declaration by Team Leads.
Development start date
Date when dev team start fixing a bug
Development end date
Date when dev team complete fixing a bug
BugFix Deploy Date
Date when BugFix is deployed, and Bug Issue is closed
PO Comment
Here will be PO team add a comment.
The text was updated successfully, but these errors were encountered: