PCDS Controls uses JIRA for issue tracking:

Signing Up for PCDSC

Sign Up for JIRA

If you've already signed up for and can log in to Confluence, you already have JIRA privileges.

If not, sign up as follows:

  1. Click the following link and fill out the Confluence/JIRA Account signup form.

  2. You should receive an e-mail within 24 hours, indicating your account has been approved.

Sign Up for the PCDSC Project

To view, create, edit, assign, and otherwise manipulate issues in the PCDSC project, you must be a member of the pcds-confluence-users permission group.

If you can edit pages in the PCDS Confluence space, you are already a member of pcds-confluence-users. If you're not sure what privileges you have, log in to Confluence and click "Preferences" in the upper-right corner of any PCDS page to review your profile, which lists all groups you belong to.

If you're not a member of pcds-confluence-users, send a request to confluence-admin and cc: perazzo@SLAC.Stanford.EDU.

Creating an Issue

1. On the PCDSC project page, click "Create a new issue in project PCDS Controls".
2. Follow the wizard, assigning Issue Type, Priority, Description and other fields as needed.
   • Note: The "Component/s" field - used to associate an issue with a Controls subsystem - is under construction. We're debating a classification scheme that will work for the whole set of experiments in the photon area.

Various Operations on an Issue 

While viewing an issue, use the "Operations" controls on the left-hand side to assign, attach files, clone, comment on, create sub-tasks, and otherwise go to town.

Scheduling Issues for a ROD 

An issue can be assigned to a "fix version," which in our case is the week in which the Controls component is scheduled to be installed. Use the "Fix Version/s" pick list on the create issue or edit issue pages.

"Labeling" Issues

The PCDSC "components" (once defined) will be the main issue classifiers. An issue can be associated with one or more components (e.g., AMOVAC and AMOSCREENS).

After a JIRA upgrade scheduled to occur before the December shutdown, an issue can also be assigned one or more "labels".

An issue on an "SXRMOTION" component could be labeled with "sxruserops" to flag it as having a significant impact on SXR users. A report based on these could give users a heads up and workarounds for the problem.

Viewing Issues

Some standard reports are available from the PCDSC project page:

• On the right side, pre-canned reports (by assignee, by issue severity, etc.)
• Under "Component/s", a report for each Controls subsystem. Subsystems are currently being defined.

Issues are displayed in the "Issue Navigator," which can be personalized.

Creating Custom Reports

1. Open any of the pre-canned reports, or from the top-level menu, select "Find Issues".
   
2. Use the menus, fields, and drop-downs on the left side to create a filter.
3. When finished, click the "View>>" button.
4. Rinse and repeat if the filter needs to be adjusted. When satisfied, follow the "Save" link and obey the wizard.
   

Accessing Custom Reports

1. In the upper-right corner of any page, follow the "Filters" link.
   
2. From the popup window that appears, select from the available reports.

Why Can't I Group By?

Well, you can - by opening a custom report in "single level group by" mode.

1. On the main PCDSC project page, follow the "Single Level Group By Report" link.
2. Pick from the list of available custom reports, then select the field to group by.

Managing Custom Reports 

On the Issue Navigator page, follow the "Manage" link.

Use the controls to subscribe to reports, make your reports public (for others to view and subscribe to), etc.

Monitoring Issues

Individual Issues

1. When viewing an issue, scroll down and on the left-hand side, follow the "Watching" link.
2. Sign up to watch the issue and get email notifications.
3. If necessary (and if allowed), add others to the issue watch list.

Subscribing to a Custom Report

Subscribe to new issues matching any custom report (filter).

See Managing Custom Reports.