Mikael Sandberg Community Champion

Best meal I had was katsu udon at the family run noodle shop in Tokyo that was only opened for lunch. The noodles were made fresh every day and you ordered your noodle portion based on numbers: 1, 2 or 3. They also made an awesome kimchi udon soup.

Hi @Frank van Aartrijk, Welcome to the Atlassian Community. You should be do this with the security scheme and change it once the issue reaches a certain status. But you would need an app to do it, like Automation for Jira, JSU or Scriptrunner. 

You should be careful assigning the application group to a JQL subscription, it can have a performance impacts on your system. It is always better to make the subscription as narrow as possible.

Yes, translations affects the whole system, it cannot be set to just one project.

Automation Lite does not allow you send out email to the assignee, you would need the regular/pro version to do that. We used to just add a comment in the issue when it was overdue before we decided to go with the paid version of Automation.

You are fetching the fields as strings, so you need to convert them to double in order sum them up. Adding as Double at the end of your def should do it: def aval = getCustomFieldValue("field1") as Double def bval = getCustomFieldValue("field2") as Double def cval = getCustomFieldValue ("field3") as Double

The priority field is a system field and cannot be renamed, so you would have to create a custom field named Severity.

Hi @SofiArkano, Welcome to Atlassian Community. The HEAD is a pointer and determine your current working revision and cannot be deleted. As you can see at the top, your repository is in a detached head state, meaning you have checked out a specific commit instead of a branch, and your changes does not belong to a specific…

Hi @Yampalla Srinivas, Welcome to the Atlassian Community. The Jira mobile app is free. Each product have one feature release each year designated as an Enterprise release, and this year it was 7.13. You can find out more about Enterprise releases here.

Hi @Ed Gray, To start using the workflow you either have to change an existing project to use the new workflow, or create a new project that uses it by configuring the workflow scheme that a project uses. See Managing your workflows for more information. 

@Xin Liu You can download the new app here, Jira Server mobile app

Hi @Kate Suchkova, Welcome to the Atlassian Community. If you would like to exclude a project from your JQL you could use project != my-project, this will get you issues from all projects except my-project. If you want to specify a subset of projects you can use project in (proj1, proj2, proj3), this will only give you…

Hi @James Wolff, Welcome to the Atlassian Community. startOfWeek() starts on the current week, so if you want to get the ones for next Tuesday you would have to use startOfWeek(10d), if your week start on Sundays.

Hi @Lucy Davies, Welcome to Atlassian Community. status CHANGED FROM "in progress" TO "closed" DURING ("2019-07-08", "2019-07-14") should get you the issues you are looking for.

Hi @Tan Welcome to the Atlassian Community. You could leave the plus sign out and just use startOfDay(5), but if you want to keep + in your JQL, you have to put the whole inc in quotes, startOfDay("+5")

Yes, if you only convert the latest code it is really simple to do. All you need to do is create the repository, clone it to a client, copy/paste your code into the Git repository and then commit and push everything back to Bitbucket. The pros is that you get up and running right away, and if needed you could also do a…

Hi @Erick Dominguez, Welcome to the Atlassian Community. You need to create a bitbucket.properties file and in it you can specify which port Bitbucket should listen to. See Changing the port that Bitbucket Server listens on for more information. 

If you are using Atlassian Cloud then contact the licensing team and they can help you get Site admin permissions. 

Hi @Ian Colwell, This might be related to the changes that Atlassian did to how they handle Atlassian accounts, see this thread for more information. You can try and go to Atlassian account profile and change the setting on the picture (mine already was set to Anyone, so had to switch to private and back again for it to…

The visibility can only be restricted if the app has a feature that allows you to do that. Also, depending on the app you could change the project permission so only a particular group/project role have time tracking permissions.

Hi @Adrija Ghosh, Welcome to Atlassian Community. Page restriction permissions are controlled by space permissions in Confluence, so if you do not have permissions to add/remove restrictions you need to contact the space admin or your Confluence admin.

No, you have to have 25+ users in order to qualify for the select support if I remember correctly. You may want to contact Licensing support and they should be able to give you a definite answer on when select support kicks in.

The only way of getting 24/7 support is to sign up for premier support, see Support Services

Hi @[deleted], Atlassian made changes related to the ID process yesterday (see Release note for July 15, 2019 for more information) that is causing this. If you go to https://id.atlassian.com/manage-profile/profile-and-visibility and adjust the setting for your profile to only me and then back to public, it will reappear…

The only way around it is to create a new sprint, close the current one and move the issue to the new sprint and start it. That will add the guideline back and also remove the asterisks.

You need to have PVCS on the client where you are doing the export/import to SVN format. Yes, you can import large files, and yes, Git LFS is part of the installation on the Bitbucket side, but on each client that will access the repository you have to install the Git LFS command-line client. Please see Git LFS for more…

You could try this, How to Change the Starting Issue Key Number in JIRA. Just make sure you test it first in a dev environment before doing it in production.

Affects Version/s and Fix Version/s (which are populated by Versions under project settings) are system fields and cannot be renamed. If you are on Jira Server you could create a new language pack and rename them in there, see Renaming System Fields in JIRA

No, the history cannot be changed from within Jira.

Check who changed the sprint field on the individual issue, it is part of the history, that should tell you who moved them out of the sprint.