...
Page Properties |
---|
Target release | 2019.5 |
---|
Epic | Jira Legacy |
---|
server | Professional Computing Resources |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 7a84689d-2237-3592-84d4-9185140d2a9a |
---|
key | PCR360-1312 |
---|
|
|
---|
Document status | |
---|
Document owner | Profile Picture |
---|
User | 5b368253349a91633c1bb4b2 |
---|
| David Engblom |
---|
Designer | |
---|
Developers | |
---|
QALast Updated | |
---|
|
Goals
- Give customers a way to save requests for later on CustomerCenter.
- Give customers the ability to edit saved Requests.
- Give customers the ability to create Requests with multiple types of Actions.
- Provide a better layout to the cart page.
- Provide a better and more useful layout to for the Request Summary page.
...
Redesigning the cart provides more flexibility to the customers and coordinators when ordering items in CustomerCenter. Many customers would like to have the ability to save their cart, or a partial cart and come back later to submit the requests in the cart. The new cart will allow the customer to not only save their requests for later, but also to submit multiple requests on the behalf of another individual, department, or multiple individuals and departments.
...
# | Title | User Story | Importance | Notes |
---|
1 | Persistent cart | A user wants to Save Requests for later. | Must Have | - The Cart will be saved as items are added. If the user logs out of the system and then back in, the cart will be restored.
- The Cart may contain multiple requests.
- The count next to the Cart Icon will indicate how many requests are in the cart, not the number of individual items in the cart.
- Clicking the Cart icon will bring the user to the cart page.
- If the Cart contains multiple requests:
- Individual actions can be moved from one request to another in the cart.
- When the user adds another item to the cart, a prompt will be displayed asking if the item should be added to an existing request or create a new request.
jiraserver | Professional Computing Resources |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 7a84689d-2237-3592-84d4-9185140d2a9a |
---|
key | PCR360-1312 |
---|
|
|
2 | Save Incomplete Requests | A user wants to save incomplete requests. | Must Have | - Allow customers to enter partial requests and save them for later.
- Fields required to submit the request do not need to be filled in before saving the request.
|
3 | Allow submitting requests individually | A user wants to submit part of the saved cart. | Must Have | - Give customers the ability to submit some, but not all requests from the cart.
- Submitted requests must specify all required information.
- Requests missing required information cannot be submitted.
- Each request will have a customizable name, limited to 30 characters. The default name will be "Request 1", "Request 2", etc.
- When the requests are submitted, the request name will be saved as a remark on the Request.
|
4 | Redesigned Cart Layout |
| Must Have | Jira Legacy | serverProfessional Computing Resources | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 7a84689d-2237-3592-84d4-9185140d2a9a |
---|
key | PCR360-2573 |
---|
|
5 | Select multiple Services and Equipment | A user wants to change or remove multiple Equipment and Service records in a single request. | Must Have | - Customers need the ability to add multiple Service and Equipment records for change or remove requests.
- The user must be able to select items for Change and Remove requests at the same time.
Jira Legacy |
---|
server | Professional Computing Resources |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId7a84689d-2237-3592-84d4-9185140d2a9a | key | PCR360-1164 |
---|
|
6 | Summary Page of Submitted Requests | A user needs to see all pending requests, including partial requests. | Must Have | - After submitting one or more Requests, the user will be presented with a summary of the Requests.
- The summary page will include a section of Requests that were not submitted and it will list the reason(s) why.
- The summary page is printable; Requests that were not submitted will be excluded from the printout.
- Each Service Request listed will include the following information:
- Service Catalog for add requests
- Service ID for change/remove requests
- Service Reference
- Owner
- Contacts
- Location
- GLA
- Jack (if required)
- List of Attachment file names
- Cost
- Each Equipment request listed will include the following information:
- Equipment catalog for add requests
- Equipment ID/Asset Tag for change/remove requests
- Owner
- Contacts
- Location
- GLA
- List of Attachment file names
- Cost
|
...
Question | Outcome |
---|
If all items in the cart are submitted, should we allow only the items with complete information to be submitted? Or block the entire cart from submission? | Incomplete items in the cart cannot be selected for submission. |
In the cart view, how can we indicate that an item is missing information? | Each request will have a label indicating whether or not the request requires additional information before submission. |
Can Equipment be moved to another Request or Action in the Cart? | No, Equipment on an Action or Request cannot be moved to another Action or Request. |
...