Plugin Help

Goto Atlassian Marketplace to buy/try the plugin yourself! 

Definition Components and Versions for the Project
Mapping plugin uses your original component and version definitions. Define your components and versions as usual. Your previously defined component and version definitions are also fine, you can use them.

Define Mapping Between Components and Versions
Plugin adds a new link to component and version section, “Component to Version Mapping”. This new feature allows you to define which versions are applicable for which components and also component specific release date and release status for the version. If you do not define any component version mapping; version selection works as before, that means you can select any version for any component.

Define Component Versions

Effective Mappings

Bundles
You can also group different components of having different versions into a bundle with a combined bundle version. You could also give your bundle a name and use that name to search all issues found or fixed in a specific release of bundle.

Bundle Definition

Bundle Definition

Bundle Content

Bundle Content

JQL Extensions
Plugin provides 2 new JQL functions to query issues at bundle level. With this JQL functions you do not need to tune your filter for different bundle releases or create a new filter. Example JQLs:

issue in affectsBundle("Release 1", "Release 2") and issue in fixedInBundle("Release 3")

Above JQL will find all issues affecting components added to bundle named “Release 1″ and “Release 2″ and fixed in “Release 3″.

Enforcement of Versions for Components and Bundles
Once you define your first mapping; version enforcement will be activated and you won’t be allowed to select unmapped component and version pairs. This enforcement will work in issue edit screen, inline edit in issue page and also for any workflow screen, as long as component field exist on the screen. If you select multiple components affects version and fix version fields will be filtered to contain only the versions applicable to all of the selected components.
If you leave component selection empty you will be allowed to select only bundle versions. If you have not defined any bundle affects version and fix versions will show all versions defined in the project setting page, in other words it will behave like you have not installed the plugin. For projects that does not define any component specific version number or any bundle version selection fields will continue to work as it was original JIRA installation without the plugin.

Component Specific Versions

Component Specific Version Selection For JIRA

Component Specific Version Selection For JIRA

Bundle Versions

Bundle Versions

Enforcement of Versions Where a Component information is not Present
You can also check validity of component and version pairs during workflow actions. This is necessary especially there is no component information. Plugin adds a “Component to version mapping validator”. This validator enables component and version selection validity check for the current issue during workflow operations. It can be configured for affects version, fix version or both (by adding validator two times).

Enforce Component Specific Versions Also at Workflow

Enforce JIRA Component Versions at Workflow

Highlight Invalid Versions for Old Issues
By the time you start to use this plugin , you may have already created lots of issues and they may have invalid component and version pair selections. In issue view page invalid version numbers will be highlighted with a different background color. Also when you try to edit any issue with invalid version number using a popup screen(issue edit page or workflow screen) this invalid versions will be automatically cleared. Similarly changing component selection will also filter values in the both version field.
If you inline edit a component field some of the previously selected version fields may be invalid for new component selections, in that case invalid version numbers are highlighted with a different background color. If you try to inline edit a version field you will be allowed to select from only valid versions for current component selections and invalid versions will be automatically removed.

Highlight Invalid Component Versions

 

Goto Atlassian Marketplace to buy/try the plugin yourself! 

19 Responses to Plugin Help

  1. Sebastien Roberge says:

    Hello,

    I am currently evaluating this plugin and I have a concern about how the Bundle version are managed.
    I would like to do, for example, an “Upgrade Package” version 2.00 that contains many version of components like expected by this plugin. Now I want to do another version of “Upgrade Package” version 2.01 that contains other fixes in the sub components.

    Now I see that it is not possible to have twice the same bundle and that the search work only with the Bundle name. So I wonder why there is a version for bundle if this is not possible to search by it and that I am in the obligation to put the version in the name (and search by the name!)

    Let me know if this is a bug and there is plan to fix this.

    Best regards

  2. denizoguz@denizoguz.com says:

    Hi Sebastien,

    I have updated bundle related JQL functions and they accept bundle version as an argument in addition to bundle name. Also bundle names are need to be unique anymore. In other words you may give your bundles the same name as long as each one is associated with a different version. Thanks your feedback. New version of the plugin (1.2.2) is already added to marketplace. I will be pleased to hear your feedback again.

  3. Brian says:

    Hi,

    On the Component Version page is there a way to sort the list by the component? I have a huge list of components and they each have multiple versions and the list is hard to maintain without any type of sorting or grouping of the versions by component.

    Thanks

    • denizoguz@denizoguz.com says:

      You are right, I will add it and release a new version today or tomorrow.

    • denizoguz@denizoguz.com says:

      Hi Brian

      New version of the plugin allows you to filter mappings, also you could sort the table using column headers if you are using JIRA 6.

  4. Deniz Oguz says:

    A new version of the plugin (1.3.0) is released and it allows free text search within component name and version name. With this you could filter mappings list. In addition to this, you could sort mappings list by clicking on the column headers if you are using JIRA 6. In addition to this feature a few bugs are also fixed.

  5. Rofl Mao says:

    Version 1.3.1 mixes up “Released Versions” and “Unreleased Versions” in the Affects Version/s and Fixes Version/s fields when creating a task.

    Additionally (and this is the worst part) it REMOVES all versions set in the Affects Version/s and Fixes Version/s fields when editing a task.

  6. denizoguz@denizoguz.com says:

    Hi Rofl,

    I could not be able to reproduce the problem you have mentioned. Which browser and JIRA version are you using?

  7. Howdy! Great plugin.

    Is there a way to use this structure to limit the version labels that appear in the planning tab of an Agile board? To be precise, I know we can filter out issues by version via JQL. What I really need is the ability to limit the version options that appear in the ‘version column’ at the left of the planning board; limiting them to a subset I select or indicate.

    Thanks for great documentation on this plugin!

  8. Tóth András says:

    Hi!
    I am just evaluating this plugin and found the following issue: I want to assign(map) the same version number (e.g. 1.0.0) to different components, but it is not permitted. I can only do it in a tricky way (at “add”, I need to assign a different verison number, then change the mapping to the intended version and ignore the error message).
    Is it the expected behavior, that during the “Add” function, the already assigned (to other compnent) version numbers are rejected?

    • denizoguz@denizoguz.com says:

      Hi,
      No it is not the expected behavior. It should allow one version to be mapped to any number of components. Could you tell me which version of plugin are you using?

  9. Rainer Burgstaller says:

    I would like to automatically import component/version mappings, or (even better) create those from my own plugin. Is this something that can be achieved?

    • denizoguz@denizoguz.com says:

      All mappings are kept in a single db table, you can insert corresponding component and version id to that table with a script.

      Another way is using REST service of the plugin (it requires admin privilege)
      URL: http://your-jira-url/rest/com.deniz.jira.mapping/latest/
      Method:POST
      Data: JSON
      {
      projectId:1004,
      componentId:1005,
      versionId:1001
      }

      3rd way is posting form-url-encoded data to http://jira-url/secure/DefineMappingModuleAction.jspa?action=add&projectKey=PUT_PROJECT_KEY_HERE
      address with following keys.
      mapping-componentId:10004
      mapping-versionId:10004
      mapping-release-date:1%2FJul%2F14
      mapping-is-released:on

      • Rainer Burgstaller says:

        Thanks a lot for the prompt support!

        • denizoguz@denizoguz.com says:

          Sorry for the late answer :(

          • Rainer Burgstaller says:

            Hi again, I tried the approach via REST with the following JSON

            {projectId:10905,
            componentId:11515,
            versionId:11344
            }

            and am getting the following error:


            2014-08-13 15:22:27,206 http-bio-8080-exec-10 ERROR admin 922x4201x2 1ibemqu 127.0.0.1 /rest/com.deniz.jira.mapping/latest/ [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
            org.codehaus.jackson.map.JsonMappingException: Can not construct instance of com.deniz.jira.versioning.CmpVersionMapping, problem: abstract types can only be instantiated with additional type information
            at [Source: org.apache.catalina.connector.CoyoteInputStream@2a6d6dd3; line: 1, column: 1]
            at org.codehaus.jackson.map.JsonMappingException.from(JsonMappingException.java:163)
            at org.codehaus.jackson.map.deser.StdDeserializationContext.instantiationException(StdDeserializationContext.java:233)
            at org.codehaus.jackson.map.deser.AbstractDeserializer.deserialize(AbstractDeserializer.java:97)
            at org.codehaus.jackson.map.ObjectMapper._readValue(ObjectMapper.java:2695)
            at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1308)
            at org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:419)

            I am using version 1.4.6 on Jira 6.1.5

          • denizoguz@denizoguz.com says:

            There were an error in 1.4.6 that prevents mapping to be created with REST interface. If you don’t mind, could you try with the new version I have emailed to you?

  10. Matt says:

    Is there a known/simple way to use this in conjunction with the VersionSync and ComponentSync plugins?

    This plugin would be super useful for us if we could define the component-version mappings once, in a master project, and have those mappings synchronized across multiple projects.

    • denizoguz@denizoguz.com says:

      Unfortunately no. After synchronizing your component and versions with VersionSync and ComponentSync you have to map them in each project :(

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>