| 1 | Your Name | Subject (capacity planning, equipment etc.) | Epic Jira (for Semestry to add) | Original Jira (For Semestry to add) | Solution Jira (For Semestry to add) | Semestry reply | Page | Test Please describe what you have tested | Test Result Please describe any issues you had while testing as thoroughly as possible. |
---|
21 | Christina | Capacity planning | | JIRAJira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| | JIRAJira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5931 |
---|
|
| -
I can write something | This is solved in a newer 8.0 maintenance version | Capacity plan - availability overview | Filtering of Room Capabilities using the Search box | Search-box does not appear to change anything |
32 | Christina | Capacity planning | | JIRAJira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| | JIRAJira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5931 |
---|
|
| - | This is solved in a newer 8.0 maintenance version | Capacity plan - availability overview | Sorting room capabilities by lowest/highest | Sort by lowest/highest availability does not seem to work |
43 | Christina | Capacity planning | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5932 |
---|
|
| Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5983 |
---|
|
| | Candidate timetable solution | Viewing candidate timetable solution | Timetable solution doesn't show anything: |
54 | Christina | Resourcing scheduled activities | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5629 |
---|
|
| Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5651 |
---|
|
| -N/A | As designed, this is the SMART view and we would only offer one ('the best') room to facilitate speedy allocation. If you are looking for further choice then move into 'beast' mode. | Adding room or Adding Staff | Adding a room or staff to a scheduled activity | When clicking 'Search available resources' only 1 room/staff is shown, always, even if more rooms are available EDIT: what if >1 room/staff needs to be allocated? |
65 | Christina | Resourcing scheduled activities | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5629 |
---|
|
| Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5651 |
---|
|
| TBA
| Will work this through with professional services | Adding room | Adding a room to a scheduled activity | Should the 'Virtual' flag be removed when adding a room to a scheduled activity? |
76 | Christina | Staff capabilities | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5651 |
---|
|
| Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-60066589 |
---|
|
| | Import | Importing staff capabilities | Staff capabilities to become available in the staff and activity CSV import file |
87 | Christina | Staff capabilities | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5651 |
---|
|
| Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6007 |
---|
|
| | API | Importing staff capabilities | Staff capabilities to become available in the API |
98 | Christina | Staff Contract | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3498 |
---|
|
| Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5651 |
---|
|
| Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6541 |
---|
|
+- New Jira to be created
”How is the Staff Contract reflected in Staff Map on Module page” ? 
| | Resourcing scheduled activities | Allocating staff to a scheduled activity | How is the staff contract reflected in staff resourcing? (same question for staff map on modules-page) |
109 | Christina | Staff Contract | Jira Legacy |
---|
server | System Jira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3498 |
---|
|
| | JIRA
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6210 |
---|
|
| - | This is solved in a newer 8.0 maintenance version | Staff contract edit | Editing staff contract | Error on server end when switching the concurrency setting on the staff contract | 1110 | Christina | Resourcing scheduled activities | | JIRAJira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5629 |
---|
|
| | | JIRA
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6395 |
---|
|
| Bug. Will create JiraSolved | Adding Staff | Allocating staff to a scheduled activity | Adding staff to scheduled activities does not work (nothing happens when clicking 'Add resources', uncaught error): | 1211 | Alan | Scheduling activities | | | Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6394 |
---|
|
| Bug. Fix developed details coming - Alan 21/04 asking Andrew to do this | Schedule page | Attempting to schedule with a staff capability | The staff capability does not match the room capabilities therefore the Activity will not schedule. The capabilities need to be checked for their resource type. |
1312 | Christina | Capacity planning | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6559 |
---|
|
| Bug. Fix in development | Availability -notification | | Notifications ('You have 128 unused capabilities: ......') on Availability section are too long to fit the screen. Should this text be wrapped? |
1413 | Christina | Capacity planning | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| | Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6559 |
---|
|
| Bug same as above (if you fix the overlong text it comes into view) | Availability | Creating capacity plan | Availability section not working/not displaying anything |
1514 | Christina | Capacity Planning | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| | Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6559 |
---|
|
| Bug. Fix in development | Activities - edit | Removing staff capabilities | Removing staff capabilities does not work |
1615 | Christina | Capacity Planning | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6559 |
---|
|
| Bug. Fix in development | Activities - edit | Adding equipment | Either adding by capabilities or by equipment not working |
1716 | Rik | Staff contracts | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3498 |
---|
|
| | TBA
| Bug. Fix in development | Staff contract edit | 2 contracts for different departments block the staff member for the entire week, not tested against the department of the activity For example: staff: VLIMA on HvAFAT | |
1817 | Rik | Staff Contracts | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3498 |
---|
|
| | Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6568 |
---|
|
| Push as part of clash work - have messaged Andrew | Staff contract scheduling | Scheduling staff with default department on Activity X, then scheduling same staff with contract on Activity Y at the same time should provoke a staff busy-ness warning/clash (staff: Rik van der Molen) | Scheduling staff with contract A does not take into account if staff is already busy on contract B. No warning, no clash shown |
1918 | Rik | Staff Contracts | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3498 |
---|
|
| - | - New Jira to be created

| | Staff contracts export | When exporting staff members, staff contracts per staff member need to be shown | There is no column for staff contracts on the staff-table, so not shown in any export |
2019 | Rik | Staff Contracts | | JIRAJira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3498 |
---|
|
| - | - | Solved in 8.1 | Staff contracts- allocation | When allocating staff members to activity, it needs to be clear on which contract the staff member is being allocated | On the Activity Edit form, it's not clear what staff contract is allocated. Staff members are shown multiple times (1x per contract), but it's not indicated which one belongs to which contract. |
2120 | Rik | Staff Capabilities | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5931 |
---|
|
| Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
Jira | serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6569 |
---|
|
| | Staff Capabilities - adding staff | Adding staff capabilities on Activity Edit does not automatically filter down the Staff drop down on the Activity Edit | |
2221 | Rik | Staff Capabilities | Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-3379 |
---|
|
| Jira Legacy |
---|
server | System JIRAJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-5931 |
---|
|
| Jira Legacy |
---|
server | System JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionJira |
---|
serverId | fc80dafe-1668-30dd-8332-084feae9e325 |
---|
key | TT-6559 |
---|
|
| Bug. Fix in development | Capacity plan - adding capablities | Multi edit staff members - adding capabilities does not work | |