Minglepublic

Add-Ons and Extras

Exchange Mingle Extras with other Minglers around the world

This is a public Custom Hive  publicRSS

Mingle Add-On

    Peter Gillard-Moss
    Mingle-JIRA Connector v2 release
    Mingle Add-On posted May 9, 2011 by Peter Gillard-Moss, last edited May 10, 2012 , tagged Development, Project Management, QA, TW Approved
    2623 Views, 7 Comments
    Name:
    Mingle-JIRA Connector v2 release
    Overview:

    A new version of the Mingle-JIRA Connector is now available.

    This is a rewritten, backwards-incompatible version of the Connector. It has the following new features:

    • removed reliance on email
    • integrates with JIRA workflow
    • allows mapping between multiple JIRA and Mingle projects
    • extended mapping of data between JIRA and Mingle
    • workflow configuration on a per project basis 

    We would welcome your feedback and suggestions on how to it could be improved. Please comment below or email support@thoughtworks.com.

    DOWNLOAD here: Linux, Windows.

    The release archives contain full documentation.

     

    Operation and workflow integration

    Users pass issues from JIRA to Mingle by triggering the handover workflow action, which moves them into a special handover status. When an issue is moved into this status a new card will be created in Mingle, with the same title and description as the issue.

    The card created in Mingle will contain a hyperlink pointing to the linked issue in JIRA. A similar link to Mingle points back to the originating JIRA issue.

    When the card is completed the JIRA issue will be automatically transitioned to the next step in the workflow.

    The Connector can handle links between multiple JIRA and Mingle projects. Each JIRA project must be linked to exactly one Mingle project (or not linked at all); each Mingle project may be linked to one or more JIRA projects.

    Data mapping

    Standard mappings

    Every card that is created in Mingle will have a property containing the key of the originating JIRA issue. The card’s title and description will match those of the issue. The card’s description will also contain a hyperlink to the issue and the issue will have a hyperlink to the card in a custom field.

    The type of card created is determined by the type of the originating issue. This mapping is configurable.

    Configurable mappings

    In addition to the standard mappings above, the Connector can map JIRA issue fields to Mingle card properties. The fields mapped and the properties that they are stored in are configurable.

    Only the following JIRA fields can be mapped:

    • Project

    • Assignee

    • Reporter

    • Created (transfers date only; doesn’t include time)

    • Due Date

    • Priority

    These values will be copied across when the card is created. There is no further synchronization between the values after card creation. Once data has been copied from the issue to the card (including the standard data described above), it can be freely modified in Mingle without being overwritten by the Connector.

    In addition to setting card property values based on issue fields, each card created by the Connector can have properties set to constant values. The properties and values are configurable.

    Deployment

    The Connector consists of two components: a JIRA plugin (Type 2) and a standalone process. The plugin responds to status changes by using the Mingle API to create cards. The standalone process monitors an event feed in Mingle’s API and triggers issue transitions using JIRA’s SOAP API.

    The standalone Connector process can be deployed on any machine that has network access to both the Mingle and JIRA APIs. It must be triggered externally and should be integrated with the standard scheduling facility of your deployment platform.

    The Connector supports Mingle 3.3 or later and JIRA 4.1, 4.2, 4.3 and 4.4.

    Physically the Connector consists of two files. The standalone component is an archive (tarball or zip) which needs to be unpacked to an appropriate location. The JIRA plugin is a jar file which must be deployed into the JIRA server.

    When deploying the Connector for the first time, a small amount of JIRA workflow modification is required to introduce the special handover status.

    Configuration

    In addition to the details of the servers and the data mapping configuration described above, all aspects of both JIRA and Mingle workflow can be configured on a per project basis. In Mingle, different workflows can be configured for different card types.

    The plugin is configured through JIRA’s administration UI. The standalone component is configured with a single text file in YAML format.

    Source Repository:
    github project

    Comment

     

    • Peter Gillard-Moss
      posted May 26, 2011 by Peter Gillard-Moss

      Updated the post to link to release 2.0.1 which includes the following fix:

      • [#976] Connector fails when JIRA returns no Actions for the issue 
    • Ben Butler-Cole
      posted October 10, 2011 by Ben Butler-Cole

      Updated the post to confirm compatibility with JIRA 4.4.

    • Ken Mohr
      posted February 20, 2012 by Ken Mohr

      Since Mingle is very customizable, we are really looking to map more fields between Jira and Mingle.  Would it be possible to obtain the java source code of the jira plugin, so we can look at extending the mapped fields?

    • Peter Gillard-Moss
      posted February 22, 2012 by Peter Gillard-Moss

      Hello Ken,

      Coincidently we have been planning to open source the connector.

      We plan to have the source code up on github sometime in the next couple of weeks.

      I will update this post with the details once we're done.

      Peter

    • Peter Gillard-Moss
      posted March 7, 2012 by Peter Gillard-Moss

      I have updated the post to add a reference to the source on github.

    • Andrew Finnell
      posted May 9, 2012 by Andrew Finnell

      It appears the integration won't work if we are using ldap for authentication? And I know the username/password I put in the file is correct.

      I get 

      ATAL 2012-05-09 13:55:31,036 Mingle 401 error occurred while requesting for http://server:8080/api/v2/projects.xml. The
      esponse body is Incorrect username or password.;

       

      Update:

       

      Been a fustrating day. :) I added the following to auth_config.yml get it to work:

        basic_auth_enabled: true
        basic_authentication: ldap
    • Ben Butler-Cole
      posted May 10, 2012 by Ben Butler-Cole

      Hi Andrew. I'm glad you've got this working. Please let us know if you have any more problems.

      -Ben