Walter Buggenhout Community Champion

Ok, check in the box there. Is the due date field on the Edit screen used for tasks in your project? Check through Project settings > Screens - locate the Task issue type and click through to the screen associated with the Edit operation.

Hi @Elvina Janušonytė, Have a look in the permission scheme of your project to see if you have schedule issues permission in your project. 

... I don't want to keep you just hanging there with the feeling I'm not answering your question. I just think it's important to be solving the right problem. So - if you do want to automate things here - in whatever way - it will be crucial to compare the sprint start date of your issues to the current date. This question…

Absolutely, Florian. I totally agree on that. Having said that you may be better of using a Kanban board with a kanban backlog rather than a scrum board, with releases to manage the organisational part of the backlog. Using sprints just adds the complexity that you need to explicitly start them at a given point in time.…

I am resuming your last question in here, @Vinod Madhappan If i try the same with updated > 4h , the query does not fetch me any result where as when i try with updated < -4h am able to get the result. Both are same right? Why does it not work with updated > 4h ?? @Walter Buggenhout _ACA IT_ Following the same example we…

I am not working for Atlassian, just volunteering in answering questions and supporting people here on the Community. So allow me not to take a stand with respect to that statement. You could always raise the suggestion directly with Atlassian through the existing support channels. No guarantees, but you start with a no.…

Hi @Harry Rombach, I am not sure if I understand your question correctly. Let me try to rephrase - correct me if I am wrong. I understand that you have consultants have an Atlassian Account and you hope that with that account, they can work in different Atlassian instances while paying only for this one account? The…

Hi @Florian Eßer, That is a very creative approach. But it feels like you are breaking more or less all the basic rules of scrum here (sorry!). When you start a sprint, it is because you want to give your team a focused set of stories / tasks / bugs to work on for a limited period of time - in the books usually 2 weeks…

Yes. That means that the update was longer in the past than 4 hours ago, right? * In your example, let's assume that now is 9 PM * 9 PM - 4 hours (-4h) would be 5 PM * Your ticket was last updated at 4 PM, which is before 5 PM => updated < -4h will show you the ticket. Updated is the system date of the last ticket update.

Hi @Vinod Madhappan, The 2nd one is correct. With some minor tweaks: Project = "ABC" AND status not in (Closed, Cancelled) AND priority in (Blocker, Critical) AND updated < -4h AND type not in ("Deployment Request", "Operational Request") ORDER BY updated DESC Updated < -4h means last update smaller than 4 hours ago

Hi @Laube, No, that is not possible. When an issue is created, it ends up in the initial status of your workflow. 

Really important this! Thx for sharing!

Hi @Sarath, Business Value IS a custom field available in Jira Software by default. The only thing you need to do in order to use it, is add the field to your screens and you are good to go.

Hi @Lea Stjepovic, Welcome to the Community! Could it be you clicked on an Epic and - as such - filtered you issues? If that's the case, you should see something like this Clicking any clear all filters link should bring back your issues. If that is not the case, would you mind sharing a screenshot of what you are seeing…

Hi @Jim Stewart, It's a bit complex, true. I don't know if you're familiar with Jira Software (JSW), but let's say the agent view in JSM is what the issue lay-out is in JSW. In short: the agent view is the layout of the issue as it is displayed internally to your agents, so not on the portal. The longer version: Atlassian…

Hi @Francois Rey, That is indeed the first step to take. You are saying slightly strange things, though. Jira Service Management is not a project in Jira Software. Both are products with specific feature sets, built on a common Jira platform that essentially offers issues, projects (as a container to store those issues in)…

Hi @Francois Rey, I think that won't be too much of a problem since JSM and JSW are different products. My guess is you will best add Jira Software as an additional product to your JSM site. The migration will normally not interfere with your current JSM, unless you may have the bad luck that some of your projects share…

Hi @Support, Do get in touch with Atlassian migration support for this. Through the link you shared (get in touch), create a Migration Support ticket. They will be able to guide you through the process. 

Hi @Joao Borges, You can do this in a couple of ways. If your project is using its own workflows (i.e. not shared with other projects), you could use a Fields Required validator to the create transition of the workflow associated with the issue type you are creating. You can find out what workflow is behind your issues…

No worries, @Bishop Justice :-) You are right about the Team field being somewhat special. The difference with what you did earlier is that a fields required validator does not manipulate data, it just checks whether anything was filled out or not. You just have to make sure that your users CAN select a team from the…

Hi @Jim Stewart, If I am getting you correctly, you are looking for the configuration of the portal screens. You can find those under Project Settings > Request Types. Every request type is a form on the portal. As you click on any request type, you will see a page with three tabs: * Agent view * Request Form * Workflow…

Yes @Bishop Justice, Just add a Fields Required validator to the create transition of the workflow associated with the issue type you are creating. You can find out what workflow is behind your issues through Project Settings > Workflows. When you edit that workflow: * Select the transition to the first status in your…

Hi @Dave Hattig, Find the cloud migration guide right here. If you have decided to migrate during Q1 next year, start by going through the guide. Next, create a migration ticket with Migration support. They'll be happy to help you with answers to all questions you may have. And most of all: take your time to thoroughly…

Here is a link to the public roadmap of Data Center. There is nothing about new navigation in there, as far as I can see. 

I am quite sure you are missing a closing bracket at the end of your test query. Try this one: Project = WECONNECT AND (status was not in (“in Approval”, “Released”, “Done”) AND status changed to "in qa" during (startOfWeek(1d), endOfWeek(1d))) Then, I'd recommend you make sure each of the separate queries is tested and…

As per your comment below: I think the problem with my query is that, I have used the the reserved words (in and for) in the search queries. i.e. "Ready for development" and "In approval". That should not be the problem as you have correctly included your status names between quotes.

Pretty sure @Till. The post you are referring too is quite old and the then fancy new Cloud navigation has since been replaced with - well - more or less the old Server navigation. Some font and color enhancements have come to the server platform too, but that has more to do with Atlassian rebranding some time back. So…

And also: given there's quite a lot of brackets involved > check if every bracket you open is also properly closed. You may be missing closing brackets after your During (date 1, date 2) statements.

Hi @Shyam Ganesh kandasamy , It is not easy to debug without the actual error message nor access to the results, but 2 recommendations: First, you could shorten your syntax a bit. I would re-write e.g the first status part as follows: AND (status was not in (“in Approval”, “Released”, “Done”) AND status changed to "in qa"…

Hi @Till, As far as I know, there is no new navigation in Confluence server. Unless I am really mistaken, navigation changes are a thing of the cloud.