This project is read-only.

1. Configuring JIRA

To configure JIRA for use with SmartAssembly Sync for JIRA®:

  1.  Create a new JIRA user, which SmartAssembly Sync for JIRA will use:
    Create New User
  2. Give the smartassembly user permission to open issues for your projects.
    It is often simplest to just make smartassembly a member of jira_administrators.
    User Browser
  3. Click Administration, then General Configuration.
  4. On the side bar, click Issue Types:
    Issue Types on the side bar
  5. Click Create New Issue Type.
  6. Add two new issue types to your JIRA installation:
    1. The first new issue type is AutoBug.
      AutoBug is the issue type which SmartAssembly Sync for JIRA uses when raising new issues.
      1. Set the Name to AutoBug.
      2. Set the Type to Standard Issue Type.
      3. Set an Icon URL.
        You might find it helpful to use the same icon as for bugs you raise normally.
        Manage Issue Types
    2. The second new issue type is SA Project Link.
      You create one SA Project Link issue in each JIRA project that has a corresponding SmartAssembly Project. The SA Project Link issue is where the mapping between JIRA and SmartAssembly is stored.
      1. Set the Name to SA Project Link.
      2. Set the Type to Standard Issue Type.
      3. Set an Icon URL.
        Add New Issue Types
  7. In the side bar, click Custom Fields:
    Custom Fields in the side bar
  8. Click Add Custom Field.
  9. Select Free text field (unlimited text), and then click Next >>.
    Create Custom Field (Step 1 of 2)
  10. Complete the details as shown in the screenshot, then click Next>>
    The details are also in the first row of the table below.
    Create Custom Field (Step 2 of 2)
  11. Select Default Screen and then click Update.
    Associate Exception Type to screens
  12. Repeat steps 9-11 for each of the custom fields below:

Field type

Field Name

Description

Search Template

Issue Types

Context

Screens

Free text field (unlimited text)

Exception Type

Deobfuscated name of the innermost exception that was thrown by a method that was processed for exception reporting.  Include the assembly, namespace and type.  Example: System.ArgumentException

Free Text Searcher

AutoBug

Global context

Default Screen

Free text field (unlimited text)

Method Type

Deobfuscated name of the class of the innermost method of the innermost exception that was processed for exception reporting.  Include the assembly, namespace, and class name.  Example: [Assembly]Namespace.Class

Free Text Searcher

AutoBug

Global context

Default Screen

Free text field (unlimited text)

Method

Deobfuscated name of the innermost method of the innermost exception that was processed for exception reporting.  Include the visibility, return type, name, arguments, and semicolon.  Example: private void Method(object argument);

Free Text Searcher

AutoBug

Global context

Default Screen

Free text field (unlimited text)

Exception Report Hash

Custom hash of the exception report.  Used for disambiguating bugs where the exception type, method type, and method are not sufficient.  Example: ErrorCode=5

Free Text Searcher

AutoBug

Global context

Default Screen

Number field

Report Count

Number of reports received.

Number range searcher

AutoBug

Global context

Default Screen

Text field (<255 characters)

Earliest Build Seen

The earliest build that this issue has been seen on.  Example: 2.2.0.3

Free Text Searcher

AutoBug

Global context

Default Screen

Text field (<255 characters)

Latest Build Seen

The latest build that this issue has been seen on.  Example: 5.1.0.243

Free Text Searcher

AutoBug

Global context

Default Screen

Text field (<255 characters)

Build Fixed On

The first build where this issue should be fixed.  Example: 5.1.0.244

Free Text Searcher

AutoBug

Global context

Default Screen

Free text field (unlimited text)

Automatic Email

If this is filled, any user that reports this issue, and gives an email address, will receive the email specified here.  The format of this field has to be exactly as follows: First line = From email address, Second line = Subject, Other lines = Body.

Free Text Searcher

AutoBug

Global context

Default Screen

 

After you have added all of the custom fields, the View Custom Fields page looks like this:
View Custom Fields

  1. In the side menu, click General Configuration.
    General Configuration in the side bar
  2. If Accept remote API calls is set to OFF:
    JIRA Options
    1. Click Edit configuration.
    2. Change Accept remote API calls to ON.
    3. Click Update.
      Accept remote API calls

Next step: 2. Create SA Project Links.

Last edited Apr 11, 2011 at 4:48 PM by dnas2, version 8

Comments

madsnissen Nov 22, 2011 at 1:22 PM 
this does not work with jira 4.4.3 and seems to require the REST API for 5.0

madsnissen Aug 15, 2011 at 12:40 PM 
What is the minimum JIRA version requirement for this tool?