Jack Brickey Expert

This is a rather old post. Unsure if OP still needs assist?

Hi @Bradley , JQL queries issues not projects so it cannot be used to accomplish your goal. You should be able to do this using the APIs or consider the Marketplace apps.

Are you confident that your user ID is included in the notification schemes of the project(s)? If so you, and you are the admin, reach out to Atlassian Support. If you are not the admin please discuss with them so that they can do so.

Hi @GA , most often the reason for something like this is that the underlying queries are different between the two. Can you confirm that the filters for the gadget and the advanced search are simply based on the project and nothing else

Hi @Rosanna Segerstedt Pillay , please contact your administrator so that they might be able to assist you with access. Depending on your deployment platform, they could make you the project lead for the given project, allowing you to make some changes.

Thi @Nicholas Frain , indeed, the first thing to address is establishing a workflow and training your agents to follow this workflow. If you intend to support your customers and use a tool like JSM to do so then it is really important to ensure that the team leverages it appropriately. There are functions within the tool…

Once an issue has been created using a form, you can Reopen the form via the detail issue view, edit and save changes. Example...

Based on what I am reading here, I think you will want to create a custom date field and associate it to your Form's date field. Then you can set up an Automation rule to update the date as desired.

Nic, can you confirm whether Scriptrunner would help here? I thought I had seen where this was the case but could certainly be mistaken.

Hi @Talha Aras , you can certainly update an issue that has been created and you can update the details of the form as well. It is unclear exactly what the issue is here and what you are attempting to do. Please elaborate on the problem you are having.

Hi @Nicholas Frain , natively there isn't a JQL function for querying internal vs. external. An addon like Scriptrunner would allow this. However, maybe you Should attempt to address the larger issue here. You are trying to ensure that customer issues receive the proper attention, correct? Assuming so there are solutions…

Given that you have two TTR fields, it very well may be that you are referencing the wrong TTR. Where is the "All issue" filter defined? Is it a custom filter that you or someone else created? If so, can you please go into that filter and check the Columns being selected and see if there are two TTR options. If so select…

Hi @Manhar Sharma , there are a lot of good posts in the community that cover creating of Epix and stories using automation. I encourage you to use the search bar and find one that might fit your needs best. In the meantime, the following is the basic logic that would be used in automation. Obviously the details of your…

Hi @Jana Jäger , you can manage the customer's access in the admin.atlassian.com area. Note that you must have for Jira administrative permissions to achieve the following. * Click on the cog in upper right * select user management * filter on GSM users and find the customers you wish to suspend. * Once you have located…

Hi @Shwetha Suresh , I would refer you to Atlassian's documentation.... overview-of-jira-cloud-products JSW-pricing JSM-pricing Generally speaking, JSW is for software development teams that want to use agile or Kanban practices. JSM is used by support organizations that need to support customers. In the case of JSM agents…

Hi @Hamza D_ , natively Jira does not have a field restriction feature. It really should be handled by process and training of users. However, you could consider creating an automation rule to notify someone if the original estimate has been updated. You will have the original estimate in the history. You could also do…

Hi @Ari Shinozaki , if you click into the Search bar in the main menu area just to the left of your avatar then you will get a pop-up. At the bottom of that pop-up you will see "view all issues". Select this and you should be taken to the advanced issue search area.

Hi @Brandon , stewing on this and came up with a thought... What if you were to create a rule like this... * trigger - issue transitioned * condition - type = subtask and Summary ~ "Subtask 3" and status = done * action - edit issue, field labels = "ST3-Done" second rule for the task action... * trigger - issue…

Got it. One more question... what does Deescalate do? Does it walk-down the escalation level or simply clear the field or something else? The reason I ask, is that since you also have the Deescalate transition from/to WIP it complicates the solution. Who performs the de-escalation?

Hi @Alex Chiu , so for Standard plans we will see daily updates?

Hi Brandon, The first thing to note is that automations happens after an event. So it can't prevent an event from happening. It can undo and change the event. Such as, let's assume that we can figure out how to analyze the status of subtask3, then we could change the status of the task from Done to Closed. The challenging…

Hi @Luis alejandro Deobarro Navarro , just to get terminology out of the way first... * A single instance of JSM we'll have hey single Help Center * A Help Center will have a Portal for each and every project defined within your JSM instance If you wish to have a unique Portal for a given customer then you can create a…

Why not use a Workflow Post Function on each transition to set your Escalation level and forego Automation?

Ah the Issue view... unfortunately, not all Field, types are available as yet, but they are working on it. You can switch to the other view as prostrated when you click on the columns icon.

Hi @Michelle.Basson , what "list" view are you referring to here? Maybe you are referring to Queues? If not can you share a screenshot?

Actually this is better...

Hi @Jack Charnley , if we can assume that's the customer is the Reporter then consider adding an "Initiator is reporter" condition. Where this would fail - request participant customer comments.

I was thinking of my bucket as I watched the news today. I would like to fly to space on Virgin Galatic!

Hi @Flaviu Dan , welcome to the community. In your scenario where your transitions are reentrant to the same status, then I would choose to add a label to an issue such as escalate. Then you can use that label as a condition in your rule. Of course, you could use something other than a label such as a custom field. With…

Hi @Frederik Vindum , sorry for the delay in getting back to you. Well, I do have a number of years under my belt using Atlassian products I am not super experienced with verifying domains. Though I have done this in my companies Jira instances in the past. In your response above, you seem to be conveying two different…