| Issue Number | 529 |
|---|---|
| Summary | [General] Add role for travel admin |
| Created | 2019-12-12 12:59:50 |
| Issue Type | Improvement |
| Submitted By | Juthe, Robin (NIH/NCI) [E] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2020-02-02 11:45:07 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.253654 |
We would like to create a new role for 1-2 travel admins. Their primary purpose would be to run hotel and reimbursement request reports, but we may want to also give them the ability to submit hotel/reimbursement requests. This could allow them to use EBMS to track all of their requests rather than rely on separate mechanisms to track paper vs. electronic (EBMS) submissions.
The story-point estimate is only for (a) creating the row in the database and (b) checking to make sure the new rôle doesn't break anything. It does not include creating menus for them to get to the reports or other capabilities they should have.
New rôle added on DEV.
Bob, should I create a separate ticket for permissions for this role? We'd like to limit their permissions to the travel section of the website and possibly the calendar.
Yes, let's use a separate ticket. You may want to take a two-pronged approach. In addition to making sure that the appropriate rôle(s) are required to bring up the other pages (to the extent that's possible), you might want to have a main menu with only Travel and Calendar on it. I'll estimate the new story points for the new ticket once you've decided what you want (and how much work we want to put into ensuring they can't bring up other pages, including read-only pages, that they might somehow find without the help of the menus.
Verified on DEV.
Verified on QA.
Verified on PROD. I added two new travel admin accounts today.
Elapsed: 0:00:00.000691