John Funk Community Champion

:-) I almost exclusively use the Old View still. They other thing you can do is leave in the New View and copy this to the end of the URL to see the card in Old View when you need to: ?oldIssueView=true

Hi @k o - Welcome to the Atlassian Community! Yes, you should be able to do that using Automation For Jira for Jira Cloud - it is now built in for free. What tool were you using in Server to accomplish your question?

Hi @Andrey_K - Welcome to the Atlassian Community! You should be able to do this with Automation for Jira. It comes free with Jira Cloud now. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get unlimited executions per month…

Hi Marco Yes, you can build a rule in Automation for Jira that does that. Create a rule based on Field value changed trigger. Then add an Action component for Assign issue. Choose Assign the issue to: User in a role Then just follow through with the rest of the values needed. 

Okay, let's try this one then :-) project = JIRA AND issuetype in (Story, Task) and (status != Done or status changed to Done AFTER startOfDay(-35)) ORDER BY updated DESC

Hi Antony, Automation For Jira just released some new functionality for that. Take a look at this thread (you will have to read down a ways):…

Hi Crisan - Welcome to the Atlassian Community! The only way I know to do something similar in cloud is by using an add-on for forms like ProForma. It is very easy to accomplish with that tool. 

You are very welcome!

Hi Jordan - Welcome to the Atlassian Community! It is supposed to be rolled out to everyone in the next month or two. But it is unknown what order instances will get it.

My understanding is that it is a permanent move to the top navigation only now.

My understanding is that all instances will be moved to the new top navigation and the old one will no longer be accessible. So the short answer is no you cannot go back anymore.

Hi @gmb1226 - This happens because Next-gen creates multiple versions of the same status (and custom fields, too!). If you limit your filter by project that is used in the gadget, that should help. But you can't just move the cards to another "In Progress" status because that might cause them to disappear off of the…

That's really weird! If you execute the query outside of the Dashboard do you get the same result (no issues)? And you have verified that each condition is indeed on the card? So if you take the date checks completely out do you see the cards you expect to see? And then leave the date checks in but take out the part about…

Great! Glad it's working for you!

So, you are using different fields on every project that need to be filled in? In other words, the filters are based on different fields and not the same one? What if you used Components to capture the values and just made the components field mandatory across those projects?

Hi @g.manger - Yes, we create boards that are based on an Epic. Jira makes you link the board to a Project, but that's only for allowing access to the board from within a project. It does not mean that only issues on that project can be seen. The issues that show up on the board are based on the filter associated with the…

Hi @Иван Каменский - Were you able to get this solved?

Hi @Carsten M - Was this able to solve your problem? 

Hi Elisabeth - Welcome to the Atlassian Community! Give this a try: project = MYPROJECT AND issuetype in (Story, Task) and status changed to Done AFTER startOfDay(-35) ORDER BY updated DESC

Hi Bayan - Welcome to the Atlassian Community! I think all of the add-ons for field level security are for the Server product and not Jira Cloud. Automation for Jira will not do it because automation only happens as a result of something else happening. It cannot prevent the event from happening itself. Typically,…

Hi Shiyas - Welcome to the Atlassian Community! My suspicion is because you are creating through a Service Desk Portal. Not sure what happens between JSD and JMWE in those cases. Have you tried to create a test record with just the Create button for the project (outside of the JSD Portal)?

Hi Jenny - Welcome to the Atlassian Community! It might be a timing issue. For the example you shared, it might be on the 2 day borderline (today is June 10 and your query says through June 8). Maybe change your query out a day just for fun to see if it shows up.

@Surfaraz Takkallapalli , I am very confused - your question does not appear to have anything to do with the description you posted. Which thing are you trying to solve?

Just to be clear - saying the issue is not empty in the same time period is redundant and would not change the results at all. The original query I provided solves your need. 🙂

That's correct. The way around that is probably with the changed to like you had in the other query above. Did that work for you? If not, what was not correct about it?

Hi Gerrie, You might refer to this issue for some more background information and follow along with the status: https://jira.atlassian.com/browse/JRACLOUD-73180 Briefly, my understanding was that the navigation was originally on the top. Then it moved to the left side and many people were not happy. So it was modified to…

I am not understanding what query you want. Any issue resolved during a specific time frame cannot be empty during that same time frame. You put in words what you want to see instead of trying to write the query first. 

Hi @Schups , Maybe I am missing something, but why can't you make the field mandatory to create the issue?

Hi @consraje - Welcome to the Atlassian Community! You can do that a couple of ways. 1. Modify the workflow for the SCC project to add a validtor for who can create. or 2. Change the Permission scheme for the project to modify the permissions for Create issue. You can then use Project Roles or Groups to control who can…

Basically, if it was Resolved during that time then it cannot also be empty during that same time. And the syntax problems are due to your using "during" which is not available in that context. You would need to use the combination of >= and <= like the end part.