Judd Garratt - Path of Trees Atlassian Partner

Hi Ashwini! There's no 'move issue' in the Jira Server REST api currently, though there is a suggestion to add this. It looks like Atlassian might be working on the corresponding issue for the Jira Cloud api, so you could reach out to them via the link in the comments on that issue and give some input.

Some other ideas if your projects don't have a 1-1 mapping with release/deployment version in Jira: * Create an epic for each small project (which can then be assigned to a release as needed) * Create a separate sprint or sprints that only contain issues for a specific small project (see parallel sprints) * Give…

Hi Rich! One potential way to solve is is by using Advanced Roadmaps which provides issue hierarchy above the epic level. In your situation you could create a 'Product' issue type and set this as the issue level above epic, providing a better grouping mechanism. If you need to group epics under a product, you could also…

Hi Bethan! If you're talking about the status breakdown of a version or epic, you can get a gadget to do this through the Epic Sum Up app.

This is a great question! Assuming the size of each of those department-specific Jira sites is not too large, you can gain many advantages from bringing these all together in one place. There is a tool for Jira Cloud called 'cloud-to-cloud migration' that can be used for the technical parts of such a shift. This works in a…

Hi Justine, Moving to Cloud is a great moment to smooth out the way Jira is being used (both high level, like how projects are organised, and also low level, like cleaning up custom fields). Kudos to you for taking a moment to focus on this! I've seen Jira used at both small and large scale and my strong suggestion is to…

Thanks for sharing this :) I was trying to setup something similar across projects for someone the other week. Your solution is what I needed.

Hi Corky, We have a similar situation where we deploy some features before releasing them. Our solution is to use the Jira 'releases' functionality for deployments (so we can still easily track what stories/bugfixes are in which deployment) and then we have a separate custom field for 'Release date' to track when a…

Hi Stanislav! You need to be an 'Editor' of a dashboard in order to share it. Even as a Jira admin, you can't share a dashboard that you're not an 'Editor' of (even if you can view it). As a workaround you could copy a dashboard that you can view (but not edit) and then share the copy. To change dashboard permissions, from…

Hi Andreson! There are two potential scenarios here. a) If you're happy for each project to have its own email address, you can set this from the 'Email requests' section in Project settings. Atlassian also has some instructions on how to configure email requests for a custom domain. You then give customers of project A…

Removed - accidental duplicate

Removed - accidental duplicate.

Issue security can't be set by 'Watchers' and automation can't be triggered by changes to 'Watchers', but there is a way to work around this (though it's not perfect). 1. In Jira admin, under 'Custom fields', create a new multi-user custom field. I called mine 'Users who can access'. Make sure to associate this field with…

My pleasure! Glad to help :)

My pleasure, glad to help!

Hi Steve, If you have Confluence, one way to do this is to create a FAQ page with anonymous access turned on and then link to it from the portal login message: * Turn on anonymous access for Confluence * Create a new space, create the FAQ page in this and then turn on anonymous access for that space * Add the link to the…

Awesome, glad to help!

Hi Graham, Permissions can get quite confusing, I hear you! You're right that switching to 'customers added to this service project only by agents and admins' is what you need. That does mean your internal users will have to be added to the other 15 service desks, but you can use customer organisations to make this easier.…

Hi Brett, You can do this with a post-function on the workflow. Create a customer user field and add it to the screen used by the relevant issue types in your JSM project. Then edit the workflow used by that issue type/s and add a post-function to the 'resolve this issue' transition. Pick the custom field you added above…

G'day! Unfortunately validators are currently ignored when transitioning from the portal. Docs here: Show a workflow transition in the portal There is an open suggestion you could vote for on this topic: Customer portal transition - validators not applied Depending on what you're using the validator for, there may be ways…

Hi Alex, I remember designing the original JSD knowledge base feature when I was still at Atlassian. We needed a way for portal-only users to view KB articles through the JSD portal without a Confluence license. To solve this, we created a new permission for Confluence spaces - ‘any active user can view’. This functions a…