ECMS - Use a JIRA request to Add/Change/Delete a User Account for the Imaging Service
This document describes how an approver for an Imaging implementation would use JIRA to request user account additions, modifications, or removals within Perceptive Content, also known as the ECM/Imaging Service.
All account changes must be done using Jira, which supports proper authorization, approval, and documentation of each request. When a Department Lead or Data Custodian creates a task in JIRA to add or change a user account for Imaging, that task is assigned to the Security Team at DoIT for resolution.
Note:If you are looking for Imaging technical support please use the information on this page to request it.
[Doc 8386 content is unavailable at this time.]
Note: Users need to have an active appointment in the Workday HR system to be approved for ECM/Imaging Service access. The Supervisory Organization for their appointment (SUP_ORG_ID) is required to complete this request. The UDDS for their appointment is required to complete this form.
Note: A Compliance Agreement is required. DoIT/SecAuth will confirm that a Compliance Agreement is on file before taking action on any account or group additions.
Log into JIRA to Create a Task to Add, Change, or Delete User Account(s) in the ECM/Imaging Service
- Log into the JIRA issue tracking product by clicking on URL:
https://msn-sis-wisc.atlassian.net/jira
- Logging in
- For folks with a NetID:
- In the ATLASSIAN "Log in to continue" screen, where it says "Enter your email" please enter netid@wisc.edu and click the "Continue" button.
- In the University of Wisconsin-Madison authentication page, enter your campus NetID and Password; press either Enter or click Log in (The JIRA home screen displays automatically.)
- For folks without a NetID:
- We recommend you use your work email address for your username and you will then be prompted to create a password upon first login. This will be a set of separate credentials you will need to keep track of going forward.
- We recommend you use your work email address for your username and you will then be prompted to create a password upon first login. This will be a set of separate credentials you will need to keep track of going forward.
- For folks with a NetID:
- IF YOU ARE UNABLE TO LOGIN TO THE ATLASSIAN CLOUD JIRA, please email Imaging-Support@DoIT.Wisc.edu
- From nearly any JIRA screen, click the [ + Create ] button along the top edge to create a new task.
- In the Create pop-up dialogue:
- In the Project field, select Imaging Security (IMAGING) from the drop-down menu.
- In the Work Type field, select Task from the drop-down menu.
- In the Summary field, enter a one-line title for the task, not the full detailed description which you'll enter later.
- In the Priority field, choose Major
- Click the Due Date field to use the Calendar control and select the desired due date.
- The Reporter field defaults to your name as the person making the request. If you are not the Data Custodian of record or an "Approver" registered with DoIT/SecAuth, you must use the drop-down to select the appropriate person. Account modifications will only be made by authorized approval of the appropriate person for the groups of documents involved.
- Click the Assignee field and type Team: Imaging Sec Req (you can click on the field selection as soon as you see it).
- Description: The 10 items listed below are required for all requests.
-
- Division of Enrollment Management (DEM/RO/CS) Only: Compliance forms in related SIS Jira ISISSEC-xxxx
- Imaging Database Environment: [PRODuction / TEST / Both]
- Change Request Type: [Add/Change/Deactivate] User
- Campus ID: Example: UW-Madison NetID, UW-Milwaukee Panther ID, etc.
- Full Name: [User's full name]
- Type of Employment: [FTE/LTE/Student]
Full UDDS (Business Unit,Division,Department,Sub-department): [Example: A067130] - Include the campus letter designation- Supervisory Organization (SUP_ORG_ID): [SO########]
- Email Address: [UserEmailAddress] NOTE: this needs to be the user's Institutional email address!
- Batch Security Required? [Yes or No]
- Group Name(s): [GroupName(s)] (all UW Madison users need the A_UW_Madison_Campus_Users group to be able to login)
- Type of Group Change: [Add/Remove]
-
- Instead of a detailed description above, you can use an attached document to specify all the details; especially if you are making the same request for multiple users. To do this, indicate "see attached document" in the Description and use the Attachment section to drag-n-drop the document(s) providing all the information. Use a table or a list to provide information that is unique for each user.
- Category: Choose User Request
- Module is not a required field. The particulars of each request must be specified in the Description field or an Attachment.
- Click the [ Create ] button
- JIRA displays the newly created task and automatically assigns a tracking identifier beginning with the word "IMAGING" followed by a number (e.g. IMAGING-2346).
- The default Status of the task will be set to Open.
- After the previous steps have been successfully completed, DoIT Security Authorizations will send an email containing a link to an online Imaging Compliance DocuSign form, as needed, for end‑users to sign. The email(s) will have the following characteristics:
From: (DocuSign via DocuSign) dse_NA3@docusign.net
Subject: DocuSign ImageNow Compliance For <Name>
To:
each end‑user from the Jira request individuallyCC:
the Reporter on the Jira request
Once the compliance form is signed and the end‑user clicks "Finish", the DocuSign form will be routed back to DoIT/SecAuth and they will complete the Imaging account request.
Please alert your user(s) to expect an email to their institutional email account with the subject line of "DocuSign ImageNow Compliance For <Name>" and that they will need to follow the link within the email to complete the DocuSign form. - For Division of Enrollment Management (DEM/RO/CS) requests: Instead of the process described in #5-h above, please insert at the top of the Description a line that references the ISISSEC Jira number for the corresponding user, like this: "Compliance forms in related SIS Jira ISISSEC-5834"