Tom Hombergs

To elaborate on the new feature: we just introduced support for sending builds and deployments into Jira (which will be visible in Jira's issue view, or the relatively new deployments...

Hi @felixveysseyre, I would suggest [Jira's Automation feature](https://www.atlassian.com/software/jira/features/automation) for this use case. With that, you can define triggers on different development events like "commit created" or "pullrequest created" and then...

Hey @felixveysseyre I'll mark this as a feature request to be evaluated at some point. Thanks for the idea!

Hi @cpp77, when you say "release", I guess you mean a release in GitHub, right? No, there is no such functionality. I'll keep this issue open as a potential idea...

Hey @tzieleniewski, we just merged a feature where you can add a file called `.jira/config.yml` to your repository in which you can define different patterns for an environment mapping: ```yaml...

Hey @ikstewa, thanks for reporting this! Jira actually provides a state called "pending" which probably should be used in this case. I don't think we have tested with GitHub environments,...

Hey @dennisroche, > Can we turn off auto-close or map it differently? Auto-closing can be triggered by "smart commits" (https://support.atlassian.com/jira-software-cloud/docs/process-issues-with-smart-commits/), i.e. a developer uses a key word in the commit...

Hey @dennisroche, understood. It seems the best solution to help you here is to have a feature in the GitHub integration that allows you to configure which repositories may send...

Hey @SimB4t1qbit, the workflow is not really user-friendly here, sorry about that. Have you tried clicking the button "Connect GitHub organization" on the main configuration screen again? The new org...

With "in combination", you mean "in combination with `@ModuleTest` (or any other scope-constraining annotation, for that matter)", so that it would look something like this, right? ```java @RunWith(SpringRunner.class) @DataJpaTest @ModuleTest...