I've attached a job with this issue.
Yes, I only have this issue when force promotion is used. If a promotion is forced and then fails, there is no way to redo the promotion.
A problem which was leading me to use force promotion: if a promotion has some improperly set criteria then it is impossible to do a regular promotion. For example, if "When the following upstream promotions are promoted" is checked but the box for it is not filled out, clicking Approve will give the "Re-execute Promotion" button, but the promotion will never execute. It does not give any reason why, but it will say upstream promotions under unmet qualifications, but the upstream promotions is blank so that doesn't really indicate anything. If you click the "Re-execute Promotion" button again, you get a 404 error. The only option at that point is to force the promotion, and if it fails you are then completely unable to execute the promotion. I did not check if this also occurs for other invalid settings than the "upstream promotions are promoted" setting.
Can anybody provide with the job/build configuration files? You can create a new dummy job/project with some dummy promotions and send me the the whole project folder (e.g.: %JENKINS_HOME%/jobs/DUMMY-JOB) I have not been able to re-produce this behavior.
you can also use the API:
{baseurl}/view/All/job/{job_name}/config.xml{baseurl}
/view/All/job/
{job_name}/promotion/process/
{promotion_name}/config.xml
e.g.:
http://localhost/view/All/job/APP-TEST/config.xml
http://localhost/view/All/job/APP-TEST/promotion/process/PROM2/config.xml
What criteria are selected?
[ ] Only when manually approved
[ ] Promote immediately once the build is complete
[ ] Promote immediately once the build is complete based on build parameters
[ ] When the following downstream projects build successfully
[ ] When the following upstream promotions are promoted
The move to the Badge is just technical term. But from the user's perspective, it shouldn't have changed.