Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

You can set up a generic vanity account to receive requests for your Orange Tracker project.  New issues will then be created from emails sent to the vanity email addresses with the following fields completed:

Email FieldIssue Field
FromReporter
SubjectSummary
Body of email

Description


To set up the vanity account, do the following:

1)  Request the vanity account if it does not already exist using the vanity account request form.  See Generic Accounts (fka Vanity)

2)  Set up proxy access to the vanity account by including the appropriate netid(s) in the proxy access group for the account in AD (your departmental support person can help with setting up a vanity account and proxy access)

2)  Log into the vanity account and redirect all email to the Orange Tracker queue. Set up a redirect rule – do not use a forward rule. If you mistakenly use a forward rule, the reporter will be the vanity account in the Orange Tracker issue.  If you use a redirect rule, the reporter will be the original sender of the email.  You may want to include deletion of the email in the redirect rule to avoid filling up the vanity account's mailbox.

3)  Request that email be configured for the Orange Tracker project by sending an email to jira@syr.edu (or include the request for email in the new project request sent to jira@syr.edu).

You may also want the jira-users group (anyone who can log into Orange Tracker, which includes people internal to SU and people external to SU) to be added to the project's Users role, unless you are only giving the vanity email address out to a limited audience.  Adding the jira-users group allows anyone to create issues in your project, including people with non-SU email addresses (ex:  gmail, outlook, hotmail, etc.).  If you have a standard permissions setup in your project, users will only be able to see issues for which they are the reporter – they won't be able to see other users' issues in your project.

 

 

 

  • No labels