Jack Brickey Expert

Hi Mick, as you have found > operator is not a supported option. Moreover you can’t leverage sprint start/end dates which would be able to accomplish your goal. There is a feature request you might watch - JRACLOUD-72007 . you might consider looking at an addon, e.g. Scriptrunner.

The most likely cause of this is that there is a post function in your workflow that is setting the resolution to fixed. Post functions happen after any execution by an individual. You can verify and correct this by going to project settings/workflows/edit and then check the post function on the transition going to…

Hi Deepthi, welcome to the Community. There are different ways to accomplish this. However, if this is something you will do regularly I would suggest the following approach. * Create a custom field (maybe called "creation year") that is a number field. Use some form of scripting to populate based upon the creation date. *…

Hi Alex, there is a long history on these avatars. They used to not exist at all and we were limited to creating quick filters per user (yuck). Later they were in fact presented as a drop down. Finally we have landed on the current implementation which show several followed by the "+" expansion option. OOTB there isn't a…

please explain further. what values are you wanting to "turn off" and exactly what does that mean? It sounds like you are talking about browser caching but I can't say that definitively.

First you might consider removing personal email info here as this is a public forum. The issue is, I think, with the fact that they were a previous user. What you likely need to do is simply re-enable them. Were they a Customer or an Agent? If a customer, go to the Admin section (click on cog upper right) > user…

thanks @Mykenna Cepek , my testing results were similar.

by "my team" do you mean Agents or Customers? Customers cannot search for existing tickets but agents could use the search box before opening an issue.

Assuming Classic project... go to project settings > issue types, click on Actions and select edit issue types 

You might look at an addon like Tempo or similar. Here is a search in the Marketplace for “vacation” - https://marketplace.atlassian.com/search?hosting=cloud&product=jira-service-desk&query=Vacation%20 

Can you share a screenshot of what you are seeing? You should be able to click on the issue key in the list and have it open the issue in the detailed view.

This is a custom field that an admin has created in your project. You can edit the ordering here > jira Admin area > issues > custom fields. Find the field, click on the ellipses to the right and choose contexts. In the next screen you can edit the values.

You must be an Agent of the JSD project to be able to edit the Reporter. Obviously if the project is a JSW project then Agents do not apply.

I see. When you say it “crashes” exactly what are you seeing? I have never witnessed what I would cause a “crash”, e.g. the SW throws an exception.

Hi Mark, Can you share an image of what you are referring to?

It is sort of a personal preference. For me it depends on the definition of the story. For example of the story is titled “develop this new functionality” then I would contend that the story should be closed and any defects are simply linked to the story and closed independently. If however the story is worded like…

How does the automation work given the variables of the actual reporter and request type? 

Hmmm, not following. Maybe this is something new in Automation? Maybe you can point me to the details.

I suggest you reach out to Atlassian Support 

If you wish to filter by Issuetype use a filter like this... project = abc and Issuetype = 123 then if you wish to add a specific epic... project = abc and Issuetype = 123 And “epic link” = abc-444

OOTB you cannot search for comment by a specific user. You will need an addon for that. You can search for all comments with “validation” as follows comment ~ “validation”

You can simply log the work but it will indicate you as the person logging the work. If you are an admin you can log in as the user and then log the work.

Did you try the “update issue Custom Field”?

Perform a JQL search based upon the label.... labels = ‘test-label’ go thru each one of the issues and display the label field and click/delete the label in question

You aren’t missing anything. It isn’t supported in Classic.

You might want to read these articles - Jira workflows here is a quick summary... * go to Project settings > workdflows * edit the workflow associated with the Issuetype in question assuming you have more Than one. Not use Diagram mode * click on the transition (line) leaving the oh hold status (box) * to the right you…

As I mentioned in my first reply you simply need to add a Post Function to all transitions leaving the on hold status. Use the function to set the custom field. You do this by editing the workflow under Project settings. 

My suspicion is a poorly written Automation rule. Can you go to project settings > automation and have a look at your rules? Be sure to inspect global rules too. If that looks ok then inspect your workflow post functions. 

So it appears this is a duplicate question 

I’m not sure I understand your question as I’m not sure what a pop up is. That said, let me see if I can assist. if by “condition” you are referring to the “Condition” you can configure in workflows - Conditions are pre-existing when executing a transition. For example, if is set a Condition that requires an Assignee…