Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to change the field the Advanced Roadmap warning relates to

Adam Waites
Contributor
July 27, 2021

Hi,

 

When we are populating dates in the Advanced Roadmap feature, we have entered dates into the fields that are in our actual tickets.

The dates for starting work, the dates for ending work and the actual Due date the work needs to be completed by, so we can see if the planning is ok. However, the due date field that the warning relates to is not one we use on our tickets. Does anyone know how I can change the field the warning looks for to see if the expected completion date is past the due date?

Thanks

1 answer

1 accepted

0 votes
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 28, 2021

Hello @Adam Waites ,

The dates can be changed in the plan settings, by selecting the cog icon next to the plan name and choosing configure:

Screen Shot 2021-07-28 at 1.24.07 PM.png

Then under the General Configuration > Scheduling you can choose a custom date field for the scheduling to use for start and end dates here:

Screen Shot 2021-07-28 at 1.23.19 PM.png

Regards,
Earl

Adam Waites
Contributor
July 29, 2021

Hi @Earl McCutcheon , thanks for the response, unfortunately that is not the answer I was looking for. Sorry think I may have described it incorrectly. I have updated those fields that you have mentioned. Start date is linked to 'Dev Start' and the end date is linked to 'Expected Completion'. However, if we populate a date in the 'Due date' field, it will give us a warning if that 'Expected Completion' date is past the 'Due date' field. I want to change the 'Due date' field to a different field we use as this 'Due date' is not on our tickets. So when we populate our Due field, the warning will work, rather than comparing the 'Expected Completion' date against the 'Due date'. I hope that makes a bit more sense?

Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 3, 2021

Hello @Adam Waites ,

The Due date field is a built-in system field tied to various features in time tracking and sprints, where custom date fields when used in Advanced roadmaps are more of a Target Start & Target End dates that were present in the previous itteration (portfolio 2.X) noting that the previously hard set target dates were removed in favor of custom date fields in the new interface (Portfolio 3.0 later changed to Advanced Roadmaps) for more flexibility in date range calculations covered in more detail here:

So the due date is a field that is requested by the initiator, i.e. project team or manager requests to execute something by x due date via the system default time tracking field,  where the auto-scheduler will use the custom target dates to schedule the issue in the plan, which will not take the start and end dates into consideration but will and flag the issue with the warning to let you know there is a conflict between the target dates used for scheduling and the desired date in place on the issue directly per the system default values.

Regards,
Earl

Adam Waites
Contributor
August 4, 2021

@Earl McCutcheon , thanks so much for your reply again on this. So in Jira there are multiple Due Date fields (not sure if people in our project have accidentally created multiple custom fields for this) and only one of them will generate the warning that the 'End Date' field is past the 'Due Date'.

I have configured the Start Date and the End Date and wanted to select our customer Due Date as the Due Date field to generate the warning. From what I am reading in your message this does not seem possible and the Due Date to generate the warning the warnings is a built in field and due to its links to other areas of the ticket cannot be changed in configuration. Is that correct?

Thanks again

Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 4, 2021

Hi @Adam Waites ,

If you are not relying on the due date fields in any way, and only plan on using the custom field for the calculations, and tracking, you can disable the warning by selecting the "Warnings" icon in the upper right of the plan window and deselecting the checkmark slider for "Issue start date or end date set beyond the due date", allowing you to bypass the check as it does not apply to your configuration for the desired date tracking in the plan. 

The option is located here:Screen Shot 2021-08-04 at 11.18.09 AM.png

Additional details on the warning settings can be seen here:

Hope this helps.

Regards,
Earl

Adam Waites
Contributor
August 5, 2021

Hey @Earl McCutcheon

Thanks again for your clarification. We wanted the warning but we wanted the due date to be based on a different field that is on our tickets. It may just be a case of duplicating the dates but that isn't a huge issue in reality. Thanks again

Like # people like this

Suggest an answer

Log in or Sign up to answer