Comments
-
Kindly have a look at this thread: https://community.atlassian.com/t5/Jira-questions/Project-email-notification-uses-system-email-address/qaq-p/83313
-
Hello, Do I understand correctly that you do not only change AD but also migrate to a different database? Then first you need to migrate to a new database and after that you can migrate to a different AD.
-
Hello, Go to the project settings -> notifications and you will be able to provide a different email address from which notifications will be sent.
-
What are the statuses in the Done column? Suppose there is the Closed status. then your query would look like this and (status != Done or (status = Done and created > -4w)) You can not query for months in JQL. Use weeks.
-
Yes, I understand you. What are the statuses in the Done column? Suppose there is the Closed status. then your query would look like this and (status != Done or (status = Done and created > -4w)) You can not query for months in JQL. Use weeks.
-
Hello, Issues, which you can see on a board, are selected by the jql filter, which is defined for this board. You should define what an old issue is and add this condition to the jql filter for your board, Let s say that an old issue is an issue, which was create more than 4 weeks ago. Then you should add to your JQL…
-
Hello, If you bought a licence, then you can go to your Atlassian account and get a developer license(there is a link in your Atlassian account in the section with the production license). This license is the same like the production license. The only thing is that in the footer of your Jira instance will be written, that…
-
It is not possible to configure mandatory fields for tickets, which come from a email. But you can configure mandatory fields for tickets from the portal. It is same as in Jira Software.
-
In Service Desk you also have projects. If you want to have categories in a project, you should use the system Components field. You can do it in Jira Software and Service Desk (Project settings -> Components). For lead times, solution and so on, you would need an add-on like Eazybi for reporting. There is a reporting…
-
Hello, It depends on what you want. Do you want this 25 users to work in Jira and have a Jira license? Jira Service Desk has customers, who do not require a license but work from the protal. Do you need SLAs? Do you need queues (that is a special UI where basically you can see filters in a more convenient way)?
-
<url part>/search?jql=labels%3DTalent%20and%20status%3D2 You should pass the whole JQL for the jql parameter jql=lables=Talent and status=2
-
Hello, Are you Jira administrator? Do you have expired licenses?
-
You are welcome! If you feel like my answer helped you, kindly mark my answer as accepted.
-
Hello, You should add the Cancelled status to the same column in the board, where the Done status is. I guess, it is the most right column in your board.
-
Hello, Here how I can apply a permission scheme for a project: If you do not have such option, it means you are not a Jira administrator
-
Hello, Go to permission helper and have a look why these users can not see this project. You can find more info about permission helper here: https://confluence.atlassian.com/adminjiracloud/using-the-permission-helper-868982879.html
-
Hello, There is no such flag. You need to add the Blocked status to the workflow for your issue and change the current status of your issues to the Blocked status.
-
@Steven F Behnke :)
-
If you switch to the old view, you will be able to add a watcher.
-
Hello, You should create an empty screen, attach to a transition, which must require a comment, then add the Required field validator to this transition. In the required field validator, you should choose the comment field.
-
Hello, There is a category entity for projects. You can find more info here: https://confluence.atlassian.com/adminjiracloud/adding-assigning-and-deleting-project-categories-844500732.html
-
It is not possible.
-
There is no permission like that. If a user can create a project, this user can add anyone to this project. This user must be a Jira administrator. You can not split these permissions.
-
It is not possible out of the box to set permissions for a single issue type.
-
There is not such permission as add or remove issue type. You should be a Jira administrator to add or remove an issue type. But Jira administrator will also give you other permissions like creating and removing permission schemes, workflow schemes and so on.
-
@Joe Pitt Thank you. I meant CAN'T. There are only three levels: Project Administrator, Jira Administrator and System Jira Administrator. That is all.
-
Hello, You can have such permissions.
-
Hello, You could use Jira Rest API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/?utm_source=%2Fcloud%2Fjira%2Fplatform%2Frest%2F&utm_medium=302#api-api-3-search-get You should send a JQL like this: labels = URGENT
-
Hello, Try to remove customers from the create issues permission in the project permission scheme. Then group all customers into organizations and when an agent creates a ticket, the agent should set the correct organization of customers. I guess, in this case all customers in the assigned organization will be able to see…
-
Hello, It is not a normal behaviour. I suspect that you have plugins, which change these dates back.