Plugin Help

Our documentation is moved to Confluence. This page is kept for the comments entered by our users.


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

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!

Our documentation is moved to Confluence. This page is kept for the comments entered by our users.

66 Responses to Plugin Help

  1. Sebastien Roberge says:


    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. 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:


    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.


    • says:

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

    • 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. 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:

    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?

    • says:

      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?

    • 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/
      Data: JSON

      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.

      • Rainer Burgstaller says:

        Thanks a lot for the prompt support!

        • says:

          Sorry for the late answer 🙁

          • Rainer Burgstaller says:

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


            and am getting the following error:

            2014-08-13 15:22:27,206 http-bio-8080-exec-10 ERROR admin 922x4201x2 1ibemqu /rest/com.deniz.jira.mapping/latest/ [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
   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.jaxrs.JacksonJsonProvider.readFrom(

            I am using version 1.4.6 on Jira 6.1.5

          • 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.

    • says:

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

  11. Tóth András says:

    By purchasing the plugin, do we have access to source code? We would like to customize the plugin, for example, allowing non-administrator users to see the component versions of a specific bundle version.
    Thank you

    • says:

      Unfortunately no, but I could add it. I was already planning to implement that. In addition to it, I will also add a new action to clone an existing bundle to easily create new ones. I will implement these features this week and let you know when it is ready.

  12. Mark says:

    Hi. I have installed your plugin and would like to know if there is REST API documentation available for it. I have also attempted to hit this endpoint, mentioned in one of your earlier responses


    but I get 404.

    Can you please give me some guidance on where to look for the REST documentation for your plugin? Thanks.

    • says:


      I have started to prepare a manual for REST interface. You can check the initial version of it from here, it is not finished but it should be enough for starting implementation.

      • Mark says:

        Deniz, thank you. I am returning to this issue, and am still having trouble accessing the most basic REST API endpoints.

        According to

        I should be able to get a list of mappings at

        curl -i -u user:pass http://jirahost/jira/rest/com.deniz.jira.mapping/latest/mappings

        but I continue to receive 404 at this endpoint.

        We are successfully using the plugin via the Web interface for many months, so I know the plugin works to that extent.

        We are running JIRA v6.2, with your plugin version 1.4.6, and are planning to update to your plugin latest. But should this simple GET of all mappings not work in 1.4.6? I must be missing something obvious, like the path prefix to your REST API extensions is wrong or some such.

        Please help.


        • says:

          Hi Mark,

          Unfortunately plugin’s REST API was very weak. I’m improving it but it is still not enough. The method you have mentioned was added in version 1.4.10, you can not use it in 1.4.6. But I am committed to add methods you need. Just tell me what you need, and I will add all of them and help you to implement what you are trying to do. The path you are using is correct if you are using atlas-run command to start a test instance. I think you could test “http://localhost:2990/jira/rest/com.deniz.jira.mapping/latest/applicable_versions?projectId=10000” method after login to see your base URL is correct. I am sure that applicable_verisions method is working in 1.4.6 version.

          • says:

            I think you are not using atlas-run, your url seems to be correct, you are just using a different port though.

  13. Tóth András says:

    Hello! Do you have any good news about the features we discussed at 23rd of September? We really would like to use these features, by implementing on our own or by you.

    • says:

      Yes, I will release the new version tonight or at worst tomorrow. Sorry that it took a little longer than I expected due to other works.

    • says:

      Version 1.4.7 is now available from marketplace. Please give it a try and let me know whether current implementation is suitable for you. It displays bundle and component versions in Project Summary view as readonly.

  14. Javier R. says:

    Some of our Administrators can’t access the Bundles section of the Administration screen. Any hint as to what the issue might be? They get back the standard 404 (Page Not Found) from Jira. Again, this only affects a few admins. The url is https://jira.***.com/secure/BundleAction!default.jspa?projectKey=***. Jira version v6.1.6#6162-sha1:7af547c.

    • says:

      Are they project administrators or jira system administrators? Anyway, I will test with several conditions and let you now. Could you tell me which version of plugins are you using?

    • says:

      This issue is resolved in 1.4.11 version of the plugin. It will be released in a few days. Sorry, it took longer than it should be.

  15. JS says:

    Just starting evaluate the plugin and notice that when creating a Bundle and you’re adding a Component to the Bundle that the Versions listed are not being limited to the versions that are tied to the Component. Is this a bug? Could this be added?


  16. Mark says:

    Deniz, I find this returns 404, even though the add-on works fine otherwise in the web UI:

    curl -u user:pass https://jirahost/jira/rest/com.deniz.jira.mapping/latest/mappings

    What is the correct path prefix preceding /com.deniz.jira.mapping/?


    • says:

      could you try
      to check your url. This should return a list of mappings applicable for the first project you have created. It may just return [] list, but it should not return an error if the url is correct.

      • Mark says:

        Thanks for the reply, Deniz.

        I still get 404 for that URL, replacing localhost with my Jira host.

        We are running version 1.4.6 of the add-on, if that helps.

        I’ll ask my Jira admin if we can examine the logs for supporting information, then I’ll get back to you.

        • says:

          Hi Mark,
          In version 1.4.6 it is normal that you get 404 error for latest mappings REST API, it is added in version 1.4.10. Please create a test JIRA site and install the latest version of the plugin.

  17. Mark says:

    Deniz, what is the HTTP response from this create-mapping call?

    POST http://localhost:2990/jira/rest/com.deniz.jira.mapping/latest/

    Does it return a mapping JSON object of some sort that includes the created mapping ID?

    Thank you.

    • says:

      It just returns HTTP status code 201 (Created).
      Please use rest API only in the version 1.4.10 or above. other than applicable_versions, rest api is not working in previous releases 🙁

  18. Bernd says:

    We do evaluation for the plugin “Component Versions” in version 1.4.12 for JIRA Server 5.2 – 6.3.15.
    We can use the related fields around the plugin. But we can not modify the JIRA filters anymore. This problem is just visible as the plugin is active. If the plugin is deactivated, all is fine.
    What is the right version of the plugin for the usage on an JIRA Server 5.2 ..?

    Thank you.

    • says:

      Hi Bernd,
      I have released 1.4.14 which contains some fixes for JIRA 5.2. Could you try with 1.4.14? In my test with that version I did not have any problems with filter modifications. If your problem continues, could you send me exact version of your JIRA (like 5.2.1 etc.) and logs of you browser window (in chrome you can access console with alt+CTRL+J). Thanks for reporting problem with 5.2.

  19. Ross Hind says:

    I’ve observed the Enforcement of Versions for Components and Bundles working fine from some screens (the create issue pop up) but not on the screen that you get to via the project administration section where when you click on “create” the screen does not come up in a pop-up. Are you aware of this?

    • says:

      Hi Ross,
      Yes, I know it. But this is behavior of JIRA, it is not displaying issue creation pop-up if you press “Create” button in administrative screen. You can check this behavior is not related with the plugin by disabling the plugin.

  20. Ross Hind says:


    Thanks for your reply. The screen to enter details does come up fine from the admin part (it’s just that it isn’t in a pop up, which is fine).

    The problem is that the component versions do not get restricted to the mapped ones (i.e. I get the default JIRA behaviour), they all appear, the plugin doesn’t work in that circumstance, on that screen only. I can send you some screen shots of what I mean if you like, it may be clearer.


  21. Ross Hind says:

    I know that no pop-up is the JIRA behavoiour, that’s fine, it’s just that the plugin no longer serves to restrict versions displayed on that screen. That’s the problem we’re having here. We’re wanting to roll out to 50 or 100 users here at Wolseley, but senior management have asked for this issue to be raised before we do that. Is it possible for you to take a look at this issue?

    • says:

      Ok, I will look at to this issue but to be honest it may not be easy to fix or may not be possible. Issue creation from administrative section is completely different. I am using pop-up events to inject new versions and these events are not fired in issue creation from administrative area. Also it does not have much usage, only admins can access there and they also usually does not create issues from there, so if fix seems difficult I would prefer to spent my effort in other areas ☹

    • says:

      Hi Ross,

      Problem is fixed and it will be available in the next version tomorrow.

  22. Ross Hind says:

    Awsome, thanks, initially we’ll be getting the 50 or 100 license.


  23. Will says:

    I’m evaluating this plugin too and I was wondering the following:
    A few posts ago a counter question was asked by you about JIRA System or project-administrators.
    Can you tell me which administrator is allowed to do which actions on the Component – Version – Bundle definitions?

    Thanks in advance

    • says:

      It is like defining versions and components in JIRA. Only project administrators allowed to define mappings and bundles. If you add JIRA administrators group to project administrators they will also permission to create mappings and bundles. If you consider this is wrong please let me know.

  24. Jean-Michel Houdart says:


    Page “Create a Project Bundle From Component Releases”
    When I click on “Found” or “Fixed” links, I obtain the following error

    Page Web inaccessible

    Il se peut que la page Web à l’adresse http://jiraprod:18080/issues/?jql=issue%20in%20affectsBundle(9) soit temporairement inaccessible ou qu’elle ait été déplacée de façon permanente à une autre adresse Web.

    In english It may be that the Web page at http: // jiraprod: 18080 / issues / JQL =% 20in% 20affectsBundle end (9) is temporarily unavailable or has been moved permanently to a new web address? .

    I have the same error when I’m trying to use the JQL function affectsBundle or fixedInBundle in a JQL request.

    Is there something missing in the configuration ?


    • says:

      I have created following issue for this CBSV-30. We will return you within today.

    • says:

      Hi Michel,
      These JQL functions does not require any configuration. I have tried both from JQL and from the link in bundle and they are working. To help me to understand the problem better can you tell me your JIRA version? Also can you try with a different browser? What happens when you enter another JQL, a simple like issue in issueHistory()?

  25. Sumedh Ganta says:


    I was trying to get list of all component and version mapping in JIRA.

    When i try to run this command, it returns nothing other than HTTP response. Can you help me why was this happening?

    Command : curl -i -u $user:$paswd -X GET

    HTTP/1.1 200 OK
    Server: Apache-Coyote/1.1
    X-AREQUESTID: 947x993733x3
    X-ASEN: SEN-2559914
    Set-Cookie: JSESSIONID=B049F730DF4A11179DAB5A7044BC2257; Path=/; HttpOnly
    X-Seraph-LoginReason: OK
    Content-Type: text/html;charset=UTF-8
    Content-Length: 0
    Date: Tue, 29 Sep 2015 22:47:28 GMT


    • says:

      @Sumedh Ganta
      Your request is correct. I have tested it locally. It is not returning an error for you. But this method returns mappings of project for which you have browse project or administer project permissions. Could you check user you are using has one of these permissions for the projects. I’m waiting for your answer. Thanks.

      • Sumedh Ganta says:

        Hi Deniz,
        I am the Jira admin and I have global permissions to browse any project

        • says:

          Thanks for the feedback Sumedh. Plugin was incorrectly handling global permissions and expecting explicit project administration level permission. I have fixed the issue and submitted latest version of the plugin. Could you try with 1.5.3 version?

          • Sumedh Ganta says:

            Hi Deniz,

            I tried upgrading it to 1.5.3, but curl command returns nothing. But I can see content on browser before and after upgrade.

        • says:

          After login to JIRA, could you try to enter to the address bar of the browser?

        • says:

          This is getting too long. Do you mind switching to email ( It could be a lot faster.

          I think there is a problem with your login. Response from the JIRA should contain “X-AUSERNAME” header but in your post it is not exist.
          Could you also try with –verbose and no-cache headers, like this:

          curl –verbose -i -u $your_user_name:$your_password -H ‘Cache-Control: no-cache’ GET

          HTTP/1.1 200 OK
          Server: Apache-Coyote/1.1
          X-AREQUESTID: 1339x274x1
          X-ASEN: SEN-2556116
          Set-Cookie: JSESSIONID=7978D294D90C802488F183AE9ACCFB5C; Path=/; HttpOnly
          X-Seraph-LoginReason: OK
          Set-Cookie: atlassian.xsrf.token=BW88-B6KG-32ZJ-RMGV|032a13f8351368344eb49e47e36ba3a70c930498|lin; Path=/
          X-ASESSIONID: w8nxdb
          X-AUSERNAME: marcus
          Cache-Control: no-cache, no-store, no-transform
          X-Content-Type-Options: nosniff
          Content-Type: application/json;charset=UTF-8
          Transfer-Encoding: chunked
          Date: Thu, 01 Oct 2015 19:19:31 GMT

  26. Neethu says:

    Hi Team,

    We are using Component Subcomponent bundle version plugin.We need following
    2 constraints to be in-place for any component version release:
    1. No new issues can be added to a component version if it is released
    2. Component version can not be released if any of the related issues is
    still in open state (i.e. not in [Closed, Resolved] state)

    E.g.: In a project, we have a component namely “Component 1”. We have
    planned release of component version 0.1, 0.2, 0.3, etc for this component
    (as fix-version).

    If 0.1 was planned to release on 4th Jan 2015 and on 4th Jan I plan to
    release it (check the box for release) then release should only be applied
    if all issues under it are closed/fixed. Else I should get a pop-up telling
    to close list of open issues under this component version.

    Once 0.1 is released then no new issue should be able to add this as its
    fix version.

    Please let us know if this is already in-place and please guide on how to
    use it. Else let us know how we can achieve it (script, etc).

    Waiting for your replay
    Neethu Jose

Leave a Reply

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