Dennis Roche

> This could probably be solved by moving to GoReleaser, which we are planning to do in the near future. that will help with 2 of 4 things. when are...

@mboudreau thanks for reply - i'm happy to close the issue.

@mboudreau, reopening this issue as related question. As we have many teams in the same GitHub organization, is there a way to associate a repo/s with the Jira Project? e.g....

> That being said, another way we've seen this done is to split up your GitHub organizations into smaller orgs and install the app into each separate one. It's not...

I'll admit it is low-risk/occurance as typically the ticket is copy/pasted from Jira to the PR. But possible situation could when it is manually entered, e.g. typos. As we have...

> It's minor, but still something to consider It is actually a deal breaker and lack of this control will block us from deploying to our enterprise. We had the...

> I mean, the alternative is that you don't have the integration at all and instead waste a lot of your developers' time doing everything manually instead of the potential...

Hi @thombergs 👋. > Does this help? No, unfortunately as this change alone won't prevent a typo-ed smart commit from associating data with an incorrect Jira project 😕. I understand...

> "sensitive" projects in our Jira sites from being updated by unauthorized users (via GitHub) ☝ the actual reason why this is an issue for our enterprise owner and our...

@rachellerathbone thanks for looking at this. > would git commit message hooks solve the problem you're having? unfortuantely no ☹️. git commit hooks are **optional** as each user needs to...