Comments
-
Hello, If you use Jira Cloud then you can use the Field required validator in the transition, where the resolution field appears. If you use Jira Server/Data Center, then you would need a plugin. For example, you could use the Power Scripts add-on:…
-
Hello, Kindly read this KB: https://confluence.atlassian.com/jirakb/limit-restrict-user-s-project-access-280069544.html
-
Are you sure that you do not have any plugins, which influence the user log in?
-
If an issue is moved to a new sprint, it means that the Sprint custom field value has been changed and you get notification about it. It is correct. An issues is moved to a new sprint if upon closing an active sprint, this issue is not situated in the most right column. It does not matter what status or resolution an issue…
-
Hello, Have a look at the atlassian-confluence.log file for errors. You can find more info here: https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html
-
Hello, You need to have a Jira Service Desk license (to be a Jira Service Desk Agent). Ask your Jira administrator grant you one
-
Hello, Go to space space settings -> permissions. And make sure that these users are granted the view permission either directly or via a group.
-
Hello, That is right. It does not matter if an issue is closed or not as long you make modifications to this issue and your notification scheme is configured to send an email. You can disable all updates to issues after issues have been closed. In this case no users can do updates and no notifications will be sent. You can…
-
You are most welcome!
-
Hello, You would need a plugin for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could add the SIL post function to the create issue transition with a code like this: if (contains(summary, "Updated…
-
There are no restrictions. If you have access to board settings, then you can change these settings
-
Thank you @Bridget
-
@Basil Baluta You have a classic project. Roadmaps are available only for next-gen projects
-
@Fabian A_ Lopez _Community Leader - Argentina_ Florida_ California_ I wish I could get the same...
-
You are most welcome!
-
Hello, Make sure that you installed the correct version of Service Desk. It should be 3.16.0 for 7.13.0
-
Hello, I guess you should enable the Sprints option in the project settings -> features.
-
Hello, There is no way to link a board to a project other than selecting issues from this project in the board filter.
-
Hello, You would need to upgrade your Confluence Server version to a newer version and then you can use the Cloud Migration Assistant for Confluence. https://marketplace.atlassian.com/apps/1219672/cloud-migration-assistant-for-confluence?hosting=server&tab=overview&_ga=2.183935855.856277697.1543736872-65270402.1526147845…
-
Hello, It is not possible yet. If you want to merge portfolio data for two jira server instances, you would need to create all portfolio data manually.
-
You are most welcome!
-
Add &fields=*all to your search rest call. You can update values with PUT /rest/api/2/issue/{issueIdOrKey}
-
Hello, I ve never heard of such plugins. Could you share a screenshot from cog item -> add-ons -> manage add-ons?
-
Hello, You need to install the Tempo Timesheets plugin.
-
Hello, The Roadmap feature is only available for a next-gen project. A next-gen project has only one board, that is why it is not possible to create two boards and connect these boards to the Roadmap.
-
Hello, You should use the search rest call and to pass to this rest call a JQL like this: assignee = XYZ You can read more about the search rest call here: GET /rest/api/2/search
-
Hello, You would need a plugin for it. You could use the Power Custom Fields Premium add-on to create a SIL custom field, which would return information about sprints for each issue. https://marketplace.atlassian.com/apps/1210749/power-custom-fields-premium?hosting=server&tab=overview The code for the custom field would be…
-
Hello, I guess, you are talking about next-gen boards. It is not possible to control the date, when an issue is removed from a next-board. It is always 14days.
-
Hello, It is saved immediately. The Save button does not exist
-
Hello, You can create a common workflow and then add conditions to certain transitions, so that these transitions would be visible only for certain users.