Mikael Sandberg Community Champion

Hi @Larry Flowers, Welcome to Atlassian Community! Without using an app that extends JQL your only option is the query that you have since default JQL do not allow you to do nested queries. I know from experience that Scriptrunner and JQL Tricks can create a better query where you can search for all initiatives and get…

Yes, that is possible. All you need to do is trigger either on when the field is updated or when the issue is created and check what value the field has. If it correspond to the value that should notify a user you need to get the users Atlassian IDs so that you can @ mention them in the comment. Have a look at How to…

Not true, the original estimate can be on the create screen too, you just have to add the time tracking field to the create screen and you will see Original Estimate when creating the issue.

You should be able to do this using the Get project role for project endpoint in an automation and then get the user's account ID from the actors list. We did something similar using that endpoint to create a report of the number of open requests that was sent to one of our Slack channels.

The new layout is using both screens and a layout, and if you go to Project settings > Request type and select request type you want to hide the field on. Then select the issue layout tab and from here you can hide fields with no values.

If you check the public roadmap you can see that this has been pushed, and is now scheduled for Q2 2023.

In order to do that you need to have an Assets field on your issue that you can select the hardware from, that will add the link to the issue in the Linked issue section in Assets.

In order to do that you have to have an Assets field on the issue where you can select hardware. Similar to what we are doing, for each service request we link it to the reporter's asset, that is how you add your issues to the Linked issues section.

Now, if you want to notify and maybe add all component leads that have a component added to and issue you could do that with automation. All you would need to do is use the web request action to get each lead via the REST API and then send them a notification/add them as watchers to the issue.

Hi @Brian M Smith Welcome to Atlassian Community! If you create an issue with multiple components that have leads the issue will be assigned to the lead who's component is furtherest to the left. Example, let's say you create an issue and add 3 components (comp1, comp2, comp3) and comp1 and comp3 both have leads, the issue…

Hi @Pan, Welcome to Atlassian Community! You can do this using Automation, the rule would look something like this:

Note that the page will not auto refresh, so if you do not reload the page it will look like the project is still there. You will get a notification down in the left hand corner once the project is deleted.

Then you need to check your field configuration, by default any fields that you add to your screen should be optional (with a few exceptions).

Hi @L, Priyanka, Welcome to Atlassian Community! You have to get the number of licenses that corresponds to the number of users that should have access to Opsgenie, so in your case you would need 100 licenses for 100 users. 

Project stay 60 days in the trash before being permanently deleted. You do have the option to remove the project from trash, if you need to speed it up.

Hi @MIchael Franck, Welcome to Atlassian Community! It all depends on the app, some apps are free for 10 users or less, while others charge a set amount. But yes, they should all adjust if you go below 10 users if you you are on a monthly subscription. 

Yes, that is possible. You just have to add the field called Time tracking to the screen(s) used by the issue types in your project. Just go to Project settings > Issues and you will find the screen schemes for each issue type and if you click on them it will take you to the screen where you can add the field.

Yes, that's possible. All you have to do is go to Settings > Issues > Custom fields and locate your field, then click on the three dot menu on the right and select Contexts and default values. From here you can add/remove/change the options.

Your other option would be to use one of the apps in the Marketplace that allows you to create roadmaps.

That is only possible if you are on Jira Premium subscription, that will give you access to Advanced roadmaps which allows you to create multiple plans for a single project.

You can find all the compliance reports for Atlassian if you go to https://www.atlassian.com/trust/compliance

The recommended way is to use Atlassian Assist with your JSM projects, and you can read more about it here. 

You could do this by creating an automation and then use {{issue.comments.last.body}} to get the last comment.

Hi @Resignola, Kelly, Welcome to Atlassian Community! You are correct, the created vs resolved report is based on the resolution field. And no, adding a Done resolution will not automatically make all issues in the Done status marked as resolved, you would still have to set the resolution when transitioning to Done. This…

You can create an automation that sets the resolution for you. I recommend using a scheduled one and use a JQL that gets all the issues that are in the done status and where resolution = unresolved. Something like this:

Make sure that you are setting the Resolution field, either as a post function on the transition to done, or manually by adding it to a screen that the transition is associated with. It is the resolution that determine if the issue is resolved or not.

You could always make that suggestion, but I am pretty sure that that it will not happen since Halp as we know it is going away next year and be part of JSM and the new virtual agent. You can read the announcement here.

The changes to epic fields are still being rolled out, so not all customers have gotten these changes yet, our instance for example has not gotten this change yet. Based on the product update the release timeframe is Between March and April 2023

Here is the documentation for it, https://plz.halp.com/article/lva4e36oi5-how-to-create-a-ticket-with-an-emoji-reaction-in-slack#private_notes

Yes, if you start your comment with the :padlock: the comment will be added as an internal note and only visible to agents.