It's not possible to have another build with the same build number.
You can rerun a build if you'd like, but that would mean that the same repository state will be used (same commits, nothing new). If you run a new build (either manually or if it gets triggered) it's always assigned a new build number.
But why would you want to reuse the same build number (and thus erase the build information - logs, artifacts) in the first place? It's always better to create a new build, and if you think the old build is expired and no longer needed, you can delete it manually or configure build expiry feature to do it periodically/autmatically.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events