Comments
-
You can add groups under User management, just click on Settings And then User management You need site admin rights to be able to do it.
-
You need to create the new repo in Github first, then you can follow these instructions on how to import your local repo into it https://help.github.com/articles/importing-a-git-repository-using-the-command-line/
-
You can turn off the credential manager by running git config --edit --system and remove helper = manager and save the change. Also run git config --edit --global and under [core] enter askpass =
-
How many licenses do you have? If you are being redirected to Atlassian Community I assume you are on a 10 user license. Atlassian changed their support policy a couple of months ago, We’re updating our support offering for server starter (10-user) licenses. You should also checkout Some reasons, why you don't get an…
-
Since you only see this on a specific machine, you may want to checkout this and see if it helps: https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/mswin32penimcunsafenativemethods/e572fda8-49e6-4c5f-ae35-27c9381f3533?auth=1
-
You could either use git filter-branch command or the BFG Repo-Cleaner tool. Have a look at this guide, https://help.github.com/articles/removing-sensitive-data-from-a-repository/
-
You need an app in order to prevent branch creations based on patterns, I have evaluated Jira Hooks for Bitbucket (server only) and it seems to do a good job. The other option would be to write a Git hook, but then you have to make sure the hook has been added to all clients.
-
The Suite Utilities for Jira will only do the validation for one specific field. If you want to validate multiple fields you could use ScriptRunner to have a scripted validator that compares all the fields you want to check.
-
Check out https://developer.atlassian.com/static/rest/bitbucket-server/latest/bitbucket-rest.html#idm140236731638960 if you are on server, https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/pullrequests/%7Bpull_request_id%7D/merge if you are using Cloud.
-
An alternative to using the embedded one is to download Git from https://git-scm.com/ and set SourceTree to use system Git.
-
If you are on Windows, all your settings for SourceTree are stored under C:\users\<your user ID>\AppData\Local\Atlassian\Sourcetree. The tabs are in the opentabs file. On mac those settings should be under ~/Library/Application Support/SourceTree/
-
Yes, according to the Supported platforms documentation it is.
-
You would need an app to do it, Suite Utilities for Jira (JSU) has a date validator, and there should be others as well.
-
Check your existing permission schemes, sounds like they are set to allow any logged in user to browse projects. Change that to either a group or project role. You will find your permission schemes under Admin > Issues > Permission Scheme.
-
Yes, you can use Confluence internal directory to create users, see https://confluence.atlassian.com/doc/configuring-user-directories-229838212.html for more information.
-
Instead of adding the user to the jira-software group, give the new group application access. You should also check all your permission schemes to make sure they are not allowing any logged on user to browse projects.
-
Did you raise a support ticket or did you post your question here? Normally if you raise a support ticket you will get an answer fairly quickly, at least that is my experience so far. If you posted your question here, could you point to the question and I may be able to help.
-
Checkout this thread and see if the workaround mentioned in there works, https://community.atlassian.com/t5/Sourcetree-questions/SourceTree-failed-to-start/qaq-p/642445/jump-to/first-unread-message 2.3.5.0 was just released, you could also try installing that one instead. The link to the installer is in the above thread.
-
The application link should not have any effect to the authentication. When you run the query to identify the administrator now, does it show that the admin is active? And before you added the admin, was Confluence stopped?
-
Is your Confluence instance connected to AD or are you just using an internal user directory. If you are using multiple, did you do the step where it moved the internal directory to be first?
-
This should hopefully help you, https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html
-
You could use card colors and base the color on queries. Have a look at https://confluence.atlassian.com/jirasoftwareserver075/customizing-cards-935562430.html for more information about customizing cards.
-
You can use filter subscription or an app like Automation Lite for Jira (if you are on JIRA Server)
-
Have you tried clearing out your browser data? That has worked in the past when my users have had issues loading JIRA in chrome.
-
I don't know about an app, but you could run a query against the database and get the information, see this KB https://confluence.atlassian.com/confkb/how-to-list-which-spaces-a-group-can-access-720636535.html
-
The reason why SourceTree is installed under C:\users... is so you do not need Admin rights to install it and they changed the installer as of 1.9.x.x+1. Checkout this blog post about it: https://blog.sourcetreeapp.com/2016/11/16/adding-staged-updates-to-sourcetree/
-
Commit all will take all your changes and add them to the commit, equivalent to git commit --all. Commit staged changes will only commit changed files that you have already added to the staging area.
-
The Issue detail view on the Board is different from the View screen. The detail view is configured under Board > Configure > Issue Detail View.
-
The license is not tied to a specific server id if it is a paid license, it only used internally for tracking, see this thread https://community.atlassian.com/t5/Jira-Software-questions/Server-id-changed-in-the-update-7-1-8-gt-... You should still be able to just copy/paste the license key and use it on your new server.
-
SourceTree is still free. Are you referring to the support expires date under my.atlassian.com? SourceTree changed how it is licensed as of 1.8.x release and you now have to use your Atlassian account to log on when you install it instead of a license file.