Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security.

JIRA add-on visibility by specific project(s)?


Kudos on the TestRail 5 release, there are many valuable changes, particularly the “Atlassian Connect add-on for JIRA Cloud” which dynamically creates linkages back to referenced JIRA issues within TestRail. This addresses a long standing usability need we’ve had.

One significant concern, the JIRA add-on affects all projects on that server instance. The TestRail users and related JIRA project, are only a small subset of global users. In this case, the 2 TestRail sections on the issue view screen are always visible - screenshot below.

JIRA does not support enabling add-ons only for specific projects, and the project’s issue “Field Configuration” option does not show TestRail sections for hiding.

Is there a way to hide the plug-in visibility or suppress functionality for specific projects? Perhaps is this an option you can configure within the add-on?



Hi Steve,

Thanks for your posting and great to hear that you like the new version! Depending on the JIRA edition you use, you can already limit the add-on to select user groups and we also want to look into adding support for projects as well. The user groups feature is currently available for the JIRA Server add-on and it’s planned to add this to the JIRA Cloud/Connect add-on as well (this is not yet possible unfortunately to implement with JIRA Cloud/Connect add-ons but will hopefully be in the future):



Would also be good to only select specific users that use the addon.
If you are in a company of 500 or more people, 30 in a a single project but only 2-4 need the TestRail addon.
Limiting by groups is already okay, but by a single user would be even better :smile:


Hi Daniel!

You would simply create a group for these users, e.g. called “TestRail”, and filter by this. It would be difficult to add another feature for each user selection, as many JIRA instances have large number of users which would make this more complicated. And the group feature already supports this use case very well.


What is the latest on supporting the group feature in the cloud version of JIRA for user management? Is there a workaround for granting specific users to TestRail if the group feature is not yet supported?

We have a cloud instance with about 100 users, but only about 20 users would need access to TestRail. How could I accomplish this without being charged for all 100 users?

Thank you!



Hi John,

The JIRA Cloud add-on has support for limiting the add-on to specific projects but not users or groups at this point. The last time we checked this it was not really possible to limit this to select users or groups and only the JIRA Server add-on has support for this (both add-ons use a completely different plugin/add-on architecture). We are happy to review this again for a future version of the add-on, thanks for your feedback and bringing this up again.



Hi Tobias / Dennis,

Is it feasible to restrict the add-on to certain issue types as well? Or is this a JIRA plugin architecture limitation?

We would like to restrict it to Requirement and Bug item types if possible.

For new feature development, we create a requirement item in JIRA, and that requirement may have multiple sub-tasks (design, coding, test design, test automation etc). We only really need the plugin to be active on the Requirement item as our TestRail Test Case is mapped back to the requirement (i.e. from the Requirement we can see if the test is passed)

We create standalone bug items in JIRA when we find defects (again, these items may have multiple sub-tasks), and then we link our TestRail test case / test result to the bug item (i.e. from the Bug we can see if the test has passed / failed)




that would be neat :slight_smile:


Hi Glenn,

That’s currently not supported by the add-on but it might be possible to implement this for JIRA Server. It’s unlikely that JIRA Cloud supports this because of the different add-on architecture but we will make sure to review this for a future version of the add-ons. Thanks for your feedback!