Walter Buggenhout Community Champion

Hi @Alice Mason, Where are you expecting to see the date reflected? Are you not seeing it filled out in the target start date custom field? Are you expecting to see it as the starting point of the timeline bar in the roadmap visualisation? Are you using different scenarios in your plan? Also: are you on cloud or data…

Hi @Yaron Norani, Yes, it does indeed work as designed. Jira remembers the last issue type you created and does indeed propose that when you create a new one. And no, there is no configuration option to change that behaviour. Hope this helps! 

Allright, that's already a step forward 😛 If you design custom workflows, you' ll need to ensure that you do fill out the resolution field as well when you transition a work item into a done status. You can do so by adding a post function to the same transition you have just set up and use Update value field to set the…

Yes. Certain changes cannot be applied to active workflows. To work around that limitation: * Create a copy of your workflow, * apply the changes you want to make to the copy of the workflow and * then replace the current workflow with the updated copy in the workflow scheme that is attached to your project. * publish the…

Hi @Saurabh Chaudhary and welcome to the Community! Only Atlassian themselves could provide real feedback on roadmap related questions and are not always able to provide that information. I can tell you that at some point resource base planning has been a feature of Plans, when it was on server and still called Portfolio…

Hi @Joshua Stokes and welcome to the Community! There's quite a bit going on in your question. If I try to focus on the main problem you are trying to solve: tickets in a Done status remain in your JSM queue and users would like to see them disappear from it then making adjustments to your workflow won't solve that. At…

Hi @Joshua Stokes and welcome to the Community! This type of messages is usually permissions related. Being an org administrator does not automatically grant you access to all projects in your instance. A benefit of having that role, is that you can - if the issue is related to permissions - grant yourself access. If you…

Hi @quentin.arnold and welcome to the Community! The technique is slightly different in team managed vs company managed projects, but in both cases you would resolve this in your workflow settings. In a team managed project, add a workflow rule to the transition to done. In this example, I used the description field to add…

* Have a look at your Plan settings > Scheduling and make sure that start date is indeed the date used as the start of your timeline. It can also be Target Start Date on data center. * After you update the date in Jira, make sure to refresh your view in Plans. You should not have to update any data there, but it does not…

If you are on Data Center (as you indeed tagged your question), forget about what I said about the timeline views, which are a cloud feature. The rest of the story still applies, as also perfectly explained by @Piet Pieters! 

Hi @Chetan Khanna and welcome to the Community! The start and end dates of a plan align with Start date and Due date in Jira work items. You can change this in a plan's settings on the scheduling tab: However, I would advise against that if you are also using timeline views in Jira projects to look at the roadmap of a…

Hi @Shashank Sejpal and welcome to the Community! A couple of things that might be helpful: it seems that you are already succeeding in pulling a list of overdue items through a Jira filter. That is already a very good and stable starting point. But you can do much more and different things with the results of that list…

When you are just looking at the hierarchy aspect of the initial question, you would have to add your new issue types at the epic level in your hierarchy configuration. If you add a level in between project and epic, that would break the parent-child relationship you currently have between existing projects and epics. So…

Hi @Bert Duhamel, The hierarchy relation between issues in Jira is defined centrally in Jira settings > Work items > Work type hierarchy and spans your entire instance. In short: any parent-child relation you create is not going to be limited to a single project. If you want specific work types to be available in a single…

Hi @Ingo Wenke, The short character limit is very intentional. If you want more extensive reporting (if that is truly what you would want to strive for on a weekly basis), you can include more extensive reports inside your short status update. Think about: * including attached files * a smartlink to a Confluence page * a…

Hi @S Alexandre Lemaire, Since this is already a slightly "aged" question, I hope you have found a solution by now already. From the screenshots you shared, I get that this is a Jira Service Management project. On top of what @Marc -Devoteam- and @Murat Seven have shared, to edit issues in a JSM project you need to be a…

Hi @S SAJEED AHMAD, and welcome to the Community! This feature is available out of the box at the task (story) and sub-task level, where it looks like this: But indeed, it isn't there at higher levels of the hierarchy. Since you indicate being on the premium plan, a plan view in advanced roadmaps Plans feature allows you…

Hi @Andrew Fallows and welcome to the Community! I can find overdue items notifications in Personal Settings > Notification settings > Digests: Hope this helps!

In a short recap: if you don't tell JQL somehow in your filter to look in a specific set of projects (either by enumerating them or more dynamically through e.g. the project category), it will search through your entire Jira instance to perform a correct search. In plans, it is not the actual result your filter returns…

The challenge lies within JQL actually. The only thing Roadmaps / Plans adds to the story is that it has a couple of limitations on the number of issues and projects that can be included in a plan. Listing projects individually is a way of telling JQL exactly what projects to search in. But, obviously, that is not very…

Hi @Anna Hanks and welcome to the Community! Can you share more details on what you (don't) see and where in the product? Just checked in my local demo instance. When I select an idea in JPD and navigate to the delivery tab, I click on the option Link a Jira work item: After doing so, a new panel pops up where I can either…

Hi @Mason W_ Foley, It is definitely not as prominent as it used to be. It is not entirely missing, though. You can find current sprint details by clicking on the Agile icon next to the complete sprint button to get that information: Hope this helps!

Suppose you want to pull all issues that were created or resolved during the previous month, you can do something like this: (created >= startOfMonth(-1) AND created <= endOfMonth(-1)) OR (resolved >= startOfMonth(-1) AND resolved <= endOfMonth(-1)) But, honestly, that filter will do nothing but give you a list of issues.…

Hi @Jeniffer Kamaraj, There is not really a JQL for created vs resolved. What you can do, is add a created vs resolved gadget on a Jira dashboard and simply add a Jira project as the source for the gadget. This will then display issues created and resolved lines on the chart, based on the created and resolved dates of the…

Aha, good point @Manoj Kumar. The way to create such filters is to actually click together a set of criteria inside the list view's filter dialog. If you're happy with the set of criteria, you can then click the little blue link Save Filter inside the dialog and that will save the filter right inside the dialog: So that is…

Yeah, that suddenly changes the entire use case, obviously. If you're using sprints, it doesn't make any sense to try and align the dates with your epics. The timeline for child issues will display start and end dates as issues get assigned to a sprint. Literally: when an item gets added to a sprint, the start and end day…

Hi @Manoj Kumar and welcome to the Community! I'm afraid I'll have to disappoint you there ... The list view and saved filters (that you can create and save from the All work view or from Filters > Search work items are different, separate views. Filters in list view work from the (visual) Filters dropdown where you can…

Then it makes sense that you don't see them on the timeline by due date, of course. If you want to see the due date displayed on the timeline, you need to change that setting to "schedule by start and due dates" -> you have to choose one method or the other. You can't have both, unfortunately.

Glad the due date got update allright - that is at least a first thing covered. That the issue does not appear on the timeline is probably a totally different thing. Can you check the board configuration in your project and make sure the setting to schedule child issues is enabled there?

I do not know your instance, @Aisha M, so I don't know. You are using a custom field in that second example filter and this may be limited by field context to a limited set of projects. The fact that it only returns 55 issues is to some extent a hint that this might be the case. Give my suggestion a try and see if it does…