Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Is it possible to configure/customize the issue's Builds and Deployments tab details?

Edited

I have a perhaps unusual scenario with our GitHub Actions integration where a single issue can interact with multiple repositories at the same time and multiple different GHA workflows of a given repository can interact with the same environment.

This is because e.g., a change in one of our open-source projects also affects some of our own/client projects, so the changes are all implemented under the umbrella of the same issue.

Now, all of those builds are communicated from GHA to Jira correctly, but the Builds tab shows a single list of workflow runs, so we can't distinguish between the same workflow running in different repositories just by looking at the list. On top of that, the Deployments tab shows only the last workflow run of a given environment, regardless of workflow/repository.

I guess what I'd like to see on these tabs is similar to how the Pull requests tab was changed recently, which now shows PRs grouped by repositories (which is a lot better than before, so thanks!).

Is there something we can configure in Jira / the GitHub repo / the workflows to provide more meaningful information here? Also, the pipeline property is "deploy" for all of them, so that should probably be the display name of the workflow instead.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events