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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why Push dialog "Push all tags" checkbox override the default found on the Tools Options Git dialog?

I started to enter a bug for this but decided to ask the question first...

The Tools, Options, Git dialog, "Push all tags to remotes" setting directs the default state of the "Push all tags" checkbox on the "Push" dialog.       That makes sense.

However, when needed, setting the "Push all tags" on the "Push" dialog RESETS the default on the Tools Options Git dialog.                                     This seems like a bug.

Tags are used at our company for formal internal and customer releases.  Only Software Configuration Managers (SCM) should ever create and thus push tags to the server.  However, even SCM personnel should have the default (Tools, Options, Git, "Push all tags to remotes") unchecked.

There is some community discussions about the problems encountered deleting, renaming, moving tags.   If everyone has the default set to UNchecked ... and it STAYS unchecked ... modifications to the tags can be done without the issue of deleted/old tags being reintroduced via the "Push" dialog "Push all tags" checkbox being checked.

Additionally, on the "Fetch" dialog, the "Fetch all tags" checkbox is NOT persistent as are the other 2 checkboxes.      This would also be helpful to make the results of deleting, renaming, moving of tags more consistent.

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 11, 2019


Thanks for your feedback. We can take a look at the behaviours and see what we can do to ensure they are consistent. Could you please copy the contents of this question across to a new ticket to under the SRCTREEWIN project?

Hi Michael,

I followed the link and got to where I think I should have been ... (I am logged in) ... selected 'Create' ... and specified SourceTree for Windows ... but the only other options that are presented is to select Issue Type (which defaulted to 'Bug', which I think is correct) ... and 'Cancel'.    ... no way to add the details from above that I entered here ... or to submit it (and add later)?!?!?



Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 25, 2019

Interesting, sorry about that. I will try to bring it to the attention of our Jira colleagues.

in the meantime I've created

OK, thanks very much!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events