Mikael Sandberg Community Champion

@Marco Tafur just click on the check mark next to my reply, that will mark your question as answered. You can also checkout the article I just published about it, https://community.atlassian.com/t5/Feedback-Forum-articles/How-and-why-to-accept-a-solution-to-your-question/ba-p/656156

Option A is the correct one. If your user directory is setup correctly new users should be listed in JIRA and all you have to do is add them to the application group. If you cannot see new users, make sure that they where added in the right node in the AD and that your base DN in JIRA is correct.

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.

You need an app to do it. If you are on JIRA Server you could use Automation for JIRA. I use the lite version to do exactly what you are looking for. I have an automation rule that will send an email if an issue has not been touched for 2 weeks in one of our projects.

The license is not tied to the 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-7-4-4/qaq-p/638438/jump-to/first-unread-message You should still be able to just copy/paste the license…

Duplicate post of https://community.atlassian.com/t5/Jira-questions/Any-way-to-search-for-the-issues-Resolved-before-the-Due-date/qaq-p/656108

Go to Tools > Options > Network and see if changing the Proxy Server Settings to use default operating system settings works. Mine was set to custom proxy settings and that is when I got the "failed to list groupings for user" error.

First of all, welcome to Atlassian Community! If you have ScriptRunner you could create a scripted validation in the workflow to check the number selected. I have not done it myself, but have a look at this thread, hopefully it will…

First off, welcome to the Atlassian Community! Have a look at this thread and see if it helps resolve it, https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-won-t-install-on-windows-7/qaq-p/652314

Okay, go to C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree and remove the passwd file and then try again. You will be asked to authenticate again.

If you create a search with the resolution the JQL help will show you available values for the field The other option is to ask your JIRA admin to give the list of available Resolution values.

Ann's answer below was better then mine.

As Walter said, you can create a new status and then add it you the workflow you want to change. Note that you cannot delete the first status from an active workflow, so you need to make a copy of it first. After that you can move the Create action to point to the new status. Repeat this for all of your workflows that you…

Have you tried to do a complete uninstall of SourceTree? Check out this KB, https://confluence.atlassian.com/sourcetreekb/how-to-wipe-sourcetree-preferences-412484640.html

If you look at the screen scheme used for the project you can see which one is used for displaying. Normally it is the screen set to the Default issue operation:

If you add the Time tracking field to the default screen (or view screen) you should be able to see it. Check your screen scheme used by the project to see which screen to edit.

Comments will be moved with the issue. If you are using restricted comments, then take a look at this KB: https://confluence.atlassian.com/jirakb/restricted-comments-disappear-after-moving-an-issue-to-a-new-project-338366874.html

Duplicate of https://community.atlassian.com/t5/Jira-questions/How-do-I-Export-and-Import-Test-Cases-from-and-to-Zephyr-for/qaq-p/653678

Duplicate of https://community.atlassian.com/t5/Jira-Software-questions/Cannot-quot-Configure-quot-the-Jira-zendesk-add-on-without/qaq-p/653687

Sorry for the late reply. The short answer is no. I do believe there is a feature request for it, but cannot find it at the moment.

You need something like ScriptRunner or JQL Tricks to do nested JQL queries. We have both apps, but I have only used JQL Tricks for advanced queries. In your case a query would look something like this in JQL Tricks: project = X AND issue not in linkedIssuesInQuery("project = X AND issue in hasLinks(\"is blocked by\"),"is…

@Tyler T looks like the latency issue is back as of this morning.

My bad, the password is set under Admin >User management > JIRA User Server, and there you also specify the IP addresses that are accepted.

The password you need when setting up the user directory is the one you specified when the application link between Confluence and JIRA was created. Since you are using a copy of your production servers, you should recreate these links so it points to your test environments instead of production.

The password you need when setting up the user directory is the one you specified when the application link between Confluence and JIRA was created. Since you are using a copy of your production servers, you should recreate these links so it points to your test environments instead of production.

You could query your database for filters that are using the component you want to change. This query should work in MySQL select * from searchrequest where reqcontent like "%component = <name>%"

To do it in ScriptRunner you would have to create a filter that gets the stories associated with the epic, something like this: issuesInEpics("issuekey = epic-123") Save that filter (in the example the filter is named Stories in Epic), and then use it in another query: filter = 'Stories in Epic' or issueFunction in…

Are your epics also labelled Icebox?

Check out this thread and see if that helps: https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-won-t-install-on-windows-7/qaq-p/652314

Check which groups have Fisheye access under Global permissions. From the screenshot it looks like your jira-users group was given access, instead of a fisheye group that only contains the users that should have the access.