galalaly / ss-scrum-tool Goto Github PK

Success Scenarios:
N/A


Failure Scenarios:
N/A


Tasks:

Success Scenarios:
N/A


Failure Scenarios:
N/A


Tasks:
Fix Permissions and user name display in Stories from S35->S38

Success Scenarios:



Failure Scenarios:



Tasks:code,documentation

Fixing permissions in the following stories :

1) create component
2) edit component
3) delete component
4) Invite user to meeting
5) Invite component to meeting

Tasks:
Code

Tasks: Code

Roles now have dynamic permissions, allowing for easy addition and removal of 
permissions to roles 
(on the fly!) 

Upgrading roles requires no change to old usage of the permission system.

Upgrading the system requires:
- Upgrading Security controller
- Upgrading view of roles
- Upgrading AJAX API for retrieving dynamically roles/permissions

Tasks: Code

Success Scenarios:



Failure Scenarios:



Tasks: code

Success Scenarios:
N/A


Failure Scenarios:
N/A


Tasks:
Fix usage of permissions and display names for S30->S34

Method should return styled name of the user depending on his status in the 
project.

Tasks: Code

[deleted issue]

Tasks:Code

Tasks: Code

Success Scenarios:
When the reporter of an impediment task tries to updates it's status, then the 
system will grant the reporter access and update the status, then show a 
confirmation message.


Failure Scenarios:
When a user tries to update the status of an impediment task, where that user 
isn't the reporter, then the system will deny the user access and show an 
access denied notification.


Tasks:
code
documentation

Success Scenarios:

Scenario 1 : change status successfully : Given the Scrum Master/Project Admin 
change the status of one of the user attendees when clicking on set attendance 
link in the toolbox in view meeting page then the system redirects to Set 
Attendance page where he can change the status of meeting attendees.

Failure Scenarios:
Scenario 1: Given the Scrum Master/Project Admin try to change the status of 
the meeting before the meeting time has passed then the link of set attendance 
will be hidden


Tasks:
Coding,Documentation.

Success Scenarios:
N/A


Failure Scenarios:
N/A


Tasks:

Success Scenarios:
- Once requested, a role's request button should be dimmed, and text changed to 
requested.
- Once granted, a role should no longer appear in the request list.

Failure Scenarios:



Tasks: Code, scenario

Success Scenarios:



Failure Scenarios:



Tasks:
code

[deleted issue]

Success Scenarios:



Failure Scenarios:



Tasks:
code

Success Scenarios:
The Project admin clicks decline on a deletion request , enters a comment to it 
and then submits that comment. The corresponding user will be notified.


Failure Scenarios:
The Project Admin clicks decline on a deletion request, but does not enter a 
comment and then clicks submit. The declination process will not occur and the 
admin will be notified that he must enter a comment.


Tasks:
- Coding.
- Docs.

Tasks: Code