Comments
-
Another option is to use a scripted validator, here is an example, https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/simple-scripted-validators.html#_requiring_a_comment_when_assignee_changed
-
This Behaviours example should help: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html#_using_a_server_side_validator_to_set_the_fix_versions_required
-
If you have ScriptRunner you could setup a Behaviour that change the comment field to required if the custom field has a value. I do something similar with two custom fields, if one is filled in then the other becomes required.
-
Just use your existing license, it is not tied to a specific server. As long as you follow the documentation on how to migrate to a new server you should be good. I have done it before without issues and we use both Jira and Bitbucket.
-
Not from within Jira, but you can do it via the REST API. Have a look at the REST API documentation. I created a script that extracts users from specific groups, get asked from time to time to provide that data.
-
Try this, make a copy of your workflow and then associate this new copy with the scheme the project is using and see if that helps.
-
Go to Settings > Workflows in your project and see if it is using the correct workflow If it is not the right workflow you need to modify the workflow scheme. Take a look at https://confluence.atlassian.com/adminjiracloud/managing-your-workflows-776636587.html I like this page, Project screens, schemes and fields because…
-
Check to make sure that the project is using the workflow that you created.
-
You could try this python script that someone created to generate a csv file of you issues in Bitbucket and then use the csv importer in Jira.
-
Where the repository is locally has not affect, as long as the root contains the .git directory. So you could when you first clone the repository put it under your www directory if you want. If you go to the repository on the command line and run git status what does it return?
-
When you moved it, did you move everything in the repository or just parts of it? The most likely reason Sourcetree does not see it as a repository is because it is missing the .git directory. This directory contains everything that Git needs, and it must be in the root of your repository.
-
Just tried it and it downloads correctly. I have noticed some issues in Chrome from time to time lately after last update that it cannot find pages, but it works fine in Firefox.
-
You may have to use the Delete instead of Remove bookmark... I just cleaned up my bookmarks and discovered that the Remove bookmark... was not working on some of the repositories.
-
So, if I understand this correctly, you moved your local repository to a different location correct? If so, try and delete the bookmark in Sourcetree (right-click on it and select Remove bookmark from folder). Then click Add and select the new location of your repository. Hopefully that will do the trick.
-
Here is the link to the download archive for Sourcetree, https://www.sourcetreeapp.com/download-archives
-
You would need an app like ScriptRunner or Power Scripts to do that.
-
You can still use Sourcetree if Bitbucket is only using HTTP, just select HTTPS as the option.
-
You could try updating it via the database, How to Get and Update JIRA License String from the Database. Just make sure you have a full backup before attempting this.
-
The only app I found for Jira that integrates with Mercurial was this one, Commit Policy for Jira (Git, SVN, Hg). Your other option is Fisheye if you do not want to use Bitbucket.
-
No, wildcard searches can only be done on text fields.
-
Does it look something like this? If so, then just click on Advanced and you will see the text box to enter your JQL in.
-
It is not possible without an app. If you are using Jira Server, check out Label Manager for Jira.
-
Also check out this KB, Bitbucket Server is reaching resource limits, git operations on the server will only use the memory you allocate for the jvm.
-
I would start of by enabling JMX, check out Enabling JMX counters for performance monitoring. We noticed performance degradation from time to time on our instance, but after increasing the heap size it is a lot better.
-
I briefly looked at the user agreement and there is nothing in there, and if you change your password it does not say anything about a policy, it only shows you if the password is week or strong. You also have the option to enable two-step authentication. You may want to send Atlassian a question and ask, you can use this…
-
Bitbucket was having some issues. You can check the status on Atlassian Status
-
Looks like Bitbucket is currently having some issues. You can check the status on Atlassian Status
-
If you are using Atlassian account as your authentication then you have no control over the password policy and are limited what data you can see, basically just when they last logged on. If you want to be able to set password policies you would need Identity Manager or G Suite.
-
The latest version of Sourcetree does not become available on the website until the staged rollout has reached 100%. Have a look at this blog post about it, https://blog.sourcetreeapp.com/2016/11/16/adding-staged-updates-to-sourcetree/
-
Here is the link to the release notes for it, https://confluence.atlassian.com/jirasoftware/jira-software-7-6-x-release-notes-938027181.html