question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Jira Software + GitHub Enterprise + Bulldozer

See original GitHub issue

Hello there,

We bump into an issue with Jira Software when a bot user like Bulldozer updating or merging PR.

We are a GitHub Enterprise + Jira Software + Bulldozer bot (https://github.com/palantir/bulldozer\) user. We use Bulldozer for automatically merging and updating PRs if all checks passed, triggering by GitHub labels.

Our problem is when the PRs are done with Bulldozer. The PR statuses don’t change. They have been left in an OPEN state. It doesn’t happen when normal GitHub users do that. We try to find out what happens but end up we don’t know what we are doing. It is better to talk to someone who can shred us some light the way Jira Software does recognise a change.

We suspected something around a user and bot type. We could not create a Jira user to be exactly the same as Bulldozer login, for example, bulldozer[bot] as [] doesn’t permit in an email address. We realised that the [bot] suffix is added automatically by GitHub to distinguish normal users from users that are associated with a GitHub App.

Is it a known issue? Has anyone experienced this so far?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:22
  • Comments:13 (7 by maintainers)

github_iconTop GitHub Comments

19reactions
fclairambcommented, Mar 5, 2020

This is true with any bot.

We do exactly the same thing at @habx using @dependabot (which is now a Github product) & probot-automerge. Most of our pull-requests are now automatically merged (once updated with the base branch and passing the CI), and they all stay in the “OPEN” state in JIRA.

Ignoring all bots is not a good idea. Please fix it.

5reactions
atrigueirocommented, May 14, 2021

Hi all,

we’ve fixed this bug and it’s now out in prod! https://github.com/integrations/jira/pull/437

Read more comments on GitHub >

github_iconTop Results From Across the Web

Integrate with GitHub Enterprise Server - Atlassian Support
Learn how to integrate your GitHub Enterprise Server account with Jira Software so your team can see development activity in the context of...
Read more >
coreos/atlassian-jira-software - Quay.io
Repository coreos/atlassian-jira-software. ... https://github.com/coreos/docker-atlassian-jira-software. Pull this container with the following Podman ...
Read more >
Chapter 38. Dozer Red Hat JBoss Fuse 6.2.1 | Red Hat Customer ...
The dozer: component provides the ability to map between Java beans using ... on the Red Hat JBoss Enterprise Application Platform (JBoss EAP)...
Read more >
Java Full Stack Developer Lead Resume Gainesville, Florida - Hire ...
9+years of professional IT experience as a Software Developer in Software ... Maven, DB2, Agile, Hudson, Jenkins, GitHub, Stash, Jira, Mockito, Log4j.
Read more >
Random :: Apache Camel
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found