How to integrate your Jira with NerdCloud

Many organizations worldwide rely on Jira to streamline and manage their business processes. The family of products can be used across a wide range of organizations - and software development teams have a lot to benefit from the ecosystem. 

If you use Jira to manage your projects, you're already up to speed with how software projects run a lot smoother when organized through Jira. Wouldn't it be nice if your software development partners would adapt to the same workflow seamlessly? 

NerdCloud does precisely that! It’s very easy to work with and will integrate into your processes and tools without a hitch. Jira is no exception - NerdCloud will blend in with your workflow effortlessly; you'll hardly notice it. 

Here's how to go about integrating your Jira with NerdCloud. But first… 

Jira Issues

Jira teams use issues to keep tabs on the tasks that need to be done.  Jira issues can be project tasks, user requirements, software bugs, among many others, depending on how your team is set up. 

You'll need to configure these issues to control who sees and works on what. Jira has several security levels and schemes you can use to manage the issues. 

Configuring Jira Issue security schemes 

Issue-level security can only be enforced by a Jira cloud admin. You also can't manage Issue security on any of Jira's free plans, so you'll need an upgraded plan to do that. 

Once a project is associated with a particular security scheme, the scheme's security level applies to all issues within the project. The security level of the parent issue applies to all sub-tasks under it. 

Before enforcing issue-level security, you'll first have to allow the relevant users to change issue-level project permissions. 

After the relevant users and groups have access, they've got to create a security scheme, then add a security level to the scheme. 

When that's done, the next step is to set a default security level for the scheme. The default security level will be used in cases where the user reporting the issue lacks the permissions to set security levels. For schemes without a default security level, the level will be set to none; that is, everyone can view the issue. 

After the security levels are set, it's time to add users to the levels. The members of a security level may be users, groups, a multi-user or group selection, a project role, or anonymous access groups. This has to be done until all the appropriate users and groups have access to the designated security levels. 

Once the security is set, assigning security schemes to your projects would follow. You can edit or remove the security levels of previous issues as you associate the project with a security scheme. 

You can also edit the issue security schemes if the need arises. The names, descriptions, and the default security level are all editable for an issue. This means that you can also copy an existing scheme similar to the one you need, then edit it to match. 

If an issue security scheme is no longer required, you can delete it, provided it is not linked to any project. If it is, you'll first have to remove any associations before deleting it. 

Once your Jira issues are set up, assign or label tasks to NerdCloud directly from your workflow and our team will start working on your project. Integration with Jira is that easy! NerdCloud will work effortlessly with your team to bring you the results you need.