You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
On the official JIRA for SourceTree, if I try to file a bug, an error appears "User [my account] doesn't have the 'Assign Issues' permission", and the bug is not posted.
Hi Kevin,
That's weird, everybody should have permissions to post bugs or feature requests. I see on your error message that it mentions the "Assign issues" permission, are you trying to assign it to someone? If you're just trying to submit your bug and are still having problems, please send us a screenshot of the form you completed so we can see if there's anything wrong.
Also, if you'd like me to submit it on your behalf, you can copy your text in the message and I'll send the bug for you.
Best regards,
Ana
No, of course I'm not trying to assign issues to anyone. I don't even see an option to do that.
Sure. GitHub auth is totally broken in SourceTree for Mac. It's been broken for at least 8 months. It's getting ridiculous.
1. If you save your GitHub account with Basic Auth, even though you've saved the password, SourceTree asks for your password 3 - 5 times whenever you commit or pull. In the password dialog, there is a "Save to keychain" checkbox, but this doesn't seem to work - I check it every time, but it continues asking for my password.
2. If you connect your GitHub account with OAuth, SourceTree is only able to pull from public repos. It cannot push to public repos, and can't access private repos at all. This is because SourceTree requests the wrong permission set (it ONLY requests public read permissions, which is totally insufficient for a Git frontend).
Occurs in SourceTree 3.2.1 (225) and earlier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kevin,
Thanks for your detailed message.
The first part seems like it's been addressed several times and I found some bugs already in relation to it, please check them out, see if they apply to your case, and comment on them if necessary. Some of them are old, but I don't want to discard the idea that this might be a regression so I'll post them here as well:
If your Github account is Enterprise, then you might be affected by this one:
For the second part of your message, I haven't been able to find an existing bug so I submitted one and you can find it at https://jira.atlassian.com/browse/SRCTREE-6866.
Hope that helps!
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.