Is there a recommended Plug-In that supports both Gitlab & Azure Dev Ops integration with Jira?

[abalantrapu1]

Will this Plug-In support NextGen Projects?

Is this Plug-in for  Cloud Atlassian?

[Adam Wride · Accepted solution]

Hello there - this is Adam Wride with BigBrassBand, the vendor supporting the Git Integration for Jira app.

We support GitLab (GitLab.com and self-hosted) as well as Azure DevOps (Cloud and self-hosted).

If you have any questions - contact us at support@bigbrassband.com.

Cheers!

[abalantrapu1]

Thanks Adam.Would be great if there is a phone # to reach out.

[Adam Wride]

Yes - we can arrange a call. Email us at support@bigbrassband.com to arrange.

Cheers,

Adam

[abalantrapu1]

I am on Trial version of this plug in and looks like JQL Searching is for Jira Server only. Any plans of extending this to Jira CLoud and if yes a timeline? 

[Adam Wride]

JQL Searching is supported in both platforms (Server/DC and Cloud), but they are different (due to the platforms).

For Jira Cloud - you will need to enable "Send Development Information to Jira Cloud" in General settings (https://d.pr/i/impbIG). 

Then you can use the following JQL:

development[commits].all > 0

development[commits].all > 15

development[pullrequests].all > 0

development[pullrequests].open > 0

More information here about Development Information in Jira Cloud.

Cheers,

Adam

[abalantrapu1]

@Adam Wride  Thanks!

[abalantrapu1]

I did turn it on and doesn't work still . 

[Adam Wride]

Note that the documentation says (top of the screen):

Only newly added commits, branches and pull requests will be uploaded to Jira Cloud when enabling the Send Development Information to Jira Cloud setting. If you wish to upload the entire history of an integration or repository - remove the integration/repository and then add the integration/repository back.

Your complete commit/branch/pull request history needs to sent to Jira Cloud for JQL to work, so you'll need to reconnect your integration(s). 

Once they are sent to Jira Cloud, you should be able to use the JQL.

Cheers,

Adam

[abalantrapu1]

Ahh! Makes sense. Thank you.

[abalantrapu1]

Is there a way to set restrictions on the "Branch Name" text field on  the "The Create Branch" Screen?

[abalantrapu1]

I do not think it still works. Does it not work for NextGen?

[Adam Wride]

Is there a way to set restrictions on the "Branch Name" text field on  the "The Create Branch" Screen?

By restrictions - do you mean - who can use the create branch feature (we have this - in the integration settings you can require Jira users to provide their own PAT from the git server: https://d.pr/i/sFW183)?

Or do you mean some kind of branch naming template based on issue type? We don't offer this currently - but have it in our backlog. If you contact us with your email - we can notify you when this ships.

For the Commits JQL, I still do not see that Jira recognizes that command?  

I will have to test it out for getting the commits later, but it does not even recognize as valid command.  

We'll need to get some specific information from you to look at this together. Can you email us at support@bigbrassband.com?

Thanks,

Adam

[abalantrapu1]

I meant Branch Naming Template.I am sending an email right now.

[abalantrapu1]

Any update on the JQL for NexGen projects? Thanks

[Adam Wride]

Hi there - 

On JQL for NextGen projects, Atlassian doesn't currently support it (based on testing). I haven't seen a statement from Atlassian on why not or when they will support it, but I expect it is coming.

[abalantrapu1]

Awesome ! Thank you.

[abalantrapu1]

Is there a way to restrict what Repos populate on the Create Branch Repository Dropdown? 

Right now I am seeing all the Repos in Source Code Management when I do the Auto-Connect.

[Adam Wride]

@abalantrapu1 -

Is there a way to restrict what Repos populate on the Create Branch Repository Dropdown? 

We have some improvements pending to improve/restrict which ones show up (like a default repository for a project).

In the integration settings - you can modify which Jira projects are associated with the integration (and thus the repositories). 

If you want to limit which repositories are shown in specific Jira projects - open the "Show integration repositories" dialog https://d.pr/i/s2WyKG, click on the repository name https://d.pr/i/JzOSWQ, then associate the repository to specific Jira project(s): https://d.pr/i/LcIf1A

This may be impractical if you have many repositories. You can pair this technique with the answer below to give yourself more ways to limit repositories / projects.

Right now I am seeing all the Repos in Source Code Management when I do the Auto-Connect.

By default - the auto-connect option will attempt connections with all the repositories that a given user (in GitHub or Azure DevOps) has access to.

You can limit the number of repositories connected in a variety of ways:

1. Create a new service user (for example called: "GIt Integration for Jira" that only has access to the repositories that you wish to connect to with Jira.

2. For GitHub - you can use Custom API Path to cal a different GitHub API to get different results (for example, you can ask for only repositories within a given org). 

3. For GitHub and Azure DevOps - you can filter the response back from the service based on name (this filter is less robust than the Custom API Path) using JMESPath filtering.

Cheers,

Adam

[abalantrapu1]

Thanks for the above answer. How often does the indexing queue run ? Time based?

[Adam Wride]

Currently it indexes ~10 minutes after finishing indexing the repositories that you have connected (if you have just a few repositories, you'll see changes within 10 minutes; if you have hundreds/thousands of repositories, then you'll see a slower update time.

These indexing mechanics will be changing later this year to be more intelligent (not updating seldom changed repositories less frequently and updating active repositories more frequently).

Having said that - we encourage you to setup webhooks to reindex your repositories more quickly. 

[abalantrapu1]

Whenever I remove and re-add the same repo of SCM in Manage Repos for the Plug-In ,I am not asked for any login credentials ? 

[Adam Wride]

Whenever I remove and re-add the same repo of SCM in Manage Repos for the Plug-In ,I am not asked for any login credentials ? 

- What type of repository is it?

- Does it connect?

- Is it a public repository?

- Are you connecting via SSH?

It would be helpful if you sent screenshots of what you're doing so we understand the context, but it wouldn't be appropriate to post publicly here. Please send to support@bigbrassband.com

[abalantrapu1]

Could you please provide us with pricing of this PLugIn

[Adam Wride]

Pricing for Git Integration for Jira Cloud

or use the Atlassian Cloud Calculator

[abalantrapu1]

Also,would need help with why we cannot connect to our Dev-Dev ADO - Jira Instances.I sent an email to  your support.

[abalantrapu1]

We would need a little more time regards to testing this out and making a purchase.Would you be able to grant us an extension of the trial period? Currently it expires on October 31 ,2019. Possibly would you be able to extend it through Nov 30 2019?  We are figuring out to get us connected in the Dev Environment

[Adam Wride]

Please contact us support@bigbrassband.com and include your SEN so we can look at what evaluation extension options are possible (please note that Atlassian handles all licensing for Atlassian Marketplace apps).   Do not post this information to this public forum. 

[abalantrapu1]

A