I see that Build jobs support ways to determine of jobs are hung up (using build time multipliers, etc)
ie; Bamboo uses two measurements to determine if a build has hung, both have to be exceeded.
That's a great feature.
It would be great if this feature could be applied to Deployment jobs. When we see Deployment jobs randomly hang, we have to manually stop the Deployment. Usually when stopping the stuck job, the next job runs perfectly fine.
This disparity between hung build and hung deployment project handling seems to be an oversight indeed - you might want to watch and vote for the following related improvements to guide Atlassian's roadmap in this regard:
Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk! We’d love to hear your thoughts on the pros and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs