Comments
-
You can turn off the 'Browse Users' global permissions and set the 'Email Visibility of users' option to hidden. Just note that this will also disable the functionality to add users to the Watchers list and change the Reporter.
-
It all depends on the order of your user directories. If you want the user to be created in your LDAP directory it has to be before the JIRA internal directory.
-
Just delete the repository locally, it will not affect your remote repository. Just make sure that before you delete it, that you have pushed all your commits to the remote. In SourceTree you just right-click on the repository bookmark and delete it, and it will ask if you want to delete just the bookmark or also the…
-
Yes, just connect GitHub to JIRA and then enable smart commit in JIRA. Here is a link to the documentation.
-
I do not have a definite answer, but my educated guess would be that as long as you do not give external users permission to access Bitbucket and Confluence they will not be able to access them even if they are linked to JIRA.
-
Have you checked the log file to see if there are any errors? Enable debug logging and then resend the email. Also, have you tried sending a test email to the user from Bitbucket?
-
As mentioned below, if you look in the sourcetree.log file you can find out which dictionary file is causing the message. In my case I had a dictionary file in my roaming profile that was causing it. You may have to check the log file multiple times until the message is not displayed anymore.
-
If you un-check "Spell check commit comment" under Tools > Options it will go away. May or may not be the intended functionality in order to bypass Windows’ own spellchecker performance issues.
-
The "total" field shows the total number returned in your JSON object. { "startAt" : 0, "maxResults" : 10, "total": 200, "values": [ { /* result 0 */ }, { /* result 1 */ }, { /* result 2 */ } ] }
-
It can be done by using issue security scheme, there you can control who can and cannot view issues.
-
Insight works with JIRA Software and you can integrate with JIRA Service Desk as well, so both options works.
-
If you are using components you can as a post function in the workflow assign the task to project/component lead developer. The other option is to use the update issue field option to set the assignee to a specific user. I would go with the first option, because then you can control who the component lead from within the…
-
fixVersion = earliestUnreleasedVersion() will exclude archived versions.
-
Did you install it as a service? If not have you started JIRA after the reboot? The start_jira.bat script is under the bin directory of your JIRA home directory.
-
It can be done using the REST API, see api/2/filter.
-
ScriptRunner should be able to do this for you. Have a look at https://answers.atlassian.com/questions/38401896.
-
You can add multiple users as Technical Contact in my.atlassian.com to give them access to the license key.
-
Your could use the REST API and create a script to remove the repositories. /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug} has an option for delete.
-
The only thing changing is the URL, as per the information: No action is required for static site owners beyond updating your links to point to https://<yoursitename>.bitbucket.io. Please note that HTTPS is required for bitbucket.io for your security.
-
Yes, SourceTree is free, it is mentioned on the web site and also when you do the install. This is what the customer agreement states in the first paragraph (which you can find in the release notes I linked to in my answer above): This Atlassian Customer Agreement (the “Agreement”) is between you and Atlassian Pty Ltd (ABN…
-
As of 1.8 they changed it so that SourceTree is no longer using a license file, instead you have to have an account on my.atlassian.com that you use to setup SourceTree with. Check out the release notes https://www.sourcetreeapp.com/update/WindowsReleaseNotes.html
-
Are you using pull requests when merging between branch 1 and branch 2? You can change the default branch for a repository under settings > repository details. The default branch will be used as the target branch when you create a pull request. But it will not prevent a user from changing the target branch.
-
Correct, currently the kanplan feature only exist in JIRA cloud, not on JIRA Server.
-
@david narciso you may want to have a look at this, Upcoming Bitbucket Pricing. Bitbucket is adding file storage as a feature next year for Git LFS.
-
Correct, the limitation does not apply if you are running a dedicated Bitbucket Server.
-
The 2Gb limit only applies to Bitbucket, not Bitbucket Server. I have repositories that are 3 - 8 Gb that are using Git LFS without any issues.
-
That is the setup I have; JIRA is where I manage all users (connected to AD) and Bitbucket and Confluence are using JIRA as their User Directory. I would recommend adding the AD as an inactive User Directory in both Bitbucket and Confluence in case your JIRA server is down for a long period of time. We had to roll back a…
-
The ScriptRunner plugin can help you with that by adding a post function that would fast track the transition on the 2nd issue when you change the 1st issue's status.
-
According to the information I found they do, but when I was looking for it we were migrating to a TDD environment, so I cannot say for sure. I would contact them directly, they are really fast at getting back to you.
-
Zephyr and TestRail both support JIRA Cloud, so they might be candidates to take a look at. I have only looked at Zephyr before when we where looking for a test management tool replacement, but at the end we went with another tool that also did requirement management.