Edit/Issues: Edit and create issues
View/Issues/Collection: View all issues
View/IssueStatus/List: View issue status
View/Issues/Single: View details of an issue
All these permissions have been grouped together in the user group "Issue Manager"
A: Select group editor
B: Select User Groups
C: Select Issue manager
D: Save User
Reporting Issues
To begin reporting issues you need to navigate to the objects page and click the Report Issue button.
In the below example i will be using products to report the issue
A: Search the product
B: Select Search Icon
C: Press product options button
D: Press Report Issue
Creating the issue report
Once you have loaded the issue widget you can play around with the editor
in the following example i will be creating an issue , categorizing it, attaching external data and pushing it to the warehouse
A: External Integrations: Optional
B: Client Optional Optional information about the ticket ex (ticketing systems ticket #)
C: External Integration Optional
D: External Key Optional
E: Tags that you would like to organize with, this can be already existing ones(an autofill window will popup once you start typing)
or brand new ones (they will be automatically created once saved)
F: Notes, once you press the plus button notes will be added, these notes can be internal(agents only) or they can be sent to the WH staff.
G: Send notes button: this button sends you to the Action Editor, where you can specify more information if you would like
Action Editor
In the following example we will use the G option from above to go to the action editor and save changes, without modifying any notes
(you can change notes if you like)
A:Options button ( all options are housed here)
B: Save changes (Saves the action and navigates back to the issue editor)
C:Undo changes( will reset work on this action to the original data, ex if you modify the notes field and want to undo this change use this option)
D: Cancel (Returns you to the Issue Editor without saving)
E:Notes that will be sent to the WH staff.
Once you press save changes you will be able to see the action in associations
Dont worry about the random codes , they will be automatically filled in by the server and are placeholders
Options and Saving
A: Save changes (Saves changes and creates a new issue)
B: Save and close(Saves changes and closes issue , No response)
C: Undo changes( undoes changes from last load)
D: Cancel(Destroys component has no use currently)
E: Save as Draft: Saves current work to draft(each browser may have 1 draft)
F: Load from draft(If draft present gives you the option to load from it)
G: Load from autosave(every change you make should trigger an autosave , you can use this incase you accidentally reload the page)
H: Debug component, may or may not be present in the future, for developers to work on fixing component issues
Viewing Issues
Press the issues tab,
Status are listed on this page and when you click an entry you will be navigated to the page
Status codes are as follows
Open->Resolving->Pending Review ->Complete
with the option of pending review to go back to open and repeat as many times as needed.
What does it look like for the fillers?
below is an image of a pick label for the above item ,
there may be many more on this page , but this is generally what it will look like
Responses
Once a filler has responded to your item the status of the issue will change to Pending Review,
You will have the option to close the issue(Save and close) or add a new note and send it to another action for additional clarity( Save)
below is an image of an issue that has been responded to.
if you require more text you can press the send button to view more.
once done here you can cancel and save and close