How to link the "due date" field with the roadmap? (classic project)

[Jannik Oberhagemann]

We recently started to use the roadmap feature in our classic software projects and we want to use the "start date" and "due date" fields to set the timeframe for our epics. 

Problem is, the "due date" field is not linked to the displayed timeline on the roadmap. Changing the date in the field does nothing to the timeline and vice versa. The "start date" works fine. 

Now the question: is there a way to "relink" the timeline in the roadmap with the "due date" field? 

[Bill Sheboy]

Hi @Jannik Oberhagemann 

Are you using the basic roadmap or the advanced roadmap (the one purchased with Jira Premier license)?

Best regards,

Bill

[Ammon Lockwood]

@Bill Sheboy I'm running into this exact same problem. We would like to use "End Date" since that's what works well in our PortfolioPlanView. In a single board though we would like to see how that team's roadmap is going. I have found that the field used by the Roadmap in the Classic Jira Project board  is using a date field called `Due`. I can't find how to map that date to the `End Date` so that we can use the fields that are already being populated by the team for the PortfolioPlanView.

Ideally we'd like to use `End Date`, however, I'd be OK even if I could just get the `Due` date picker to show up on the Epic so we can set the Due Date without having to use the slider.

[Ammon Lockwood]

I found the field that the roadmap uses. It's `Due date` with date lowercase. I was able to add that as a field that could be added to the Epic screen view so that we can at least set the due date for the roadmap. Unfortunate that we have to put the "end date" in twice

[Jannik Oberhagemann]

@[deleted] we use the basic roadmap. As far as I know, this should not have an influence on the epic timeline in the roadmap, only on tasks in the epic. 

We tried using "end date" and "due date" non of them work. Our "start date" is tagged as "locked" in the field overview, neither end nor due date is. I think someone deleted them at some point and then they were recreated and these are not the original date picker or something like this. 

[Bill Sheboy]

Hi there!  It appears this topic split into 2 questions.  ;^)

@Jannik Oberhagemann   The locked fields are the built-in or add-on fields essential for Jira to work.  If someone deleted Due Date and re-added it, I am unclear how you can fix that.  Please consider asking your site admin to contact support for their guidance:

https://support.atlassian.com/contact/#/

@Ammon Lockwood   If you want to set your End Date and have it duplicate in Due Date (so the road map works), please consider adding an Automation Rule.  That rule could detect when the End Date changes and then copy it to Due Date.  Please see here for information about automation to get you started:

https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465

https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453

Best regards,

Bill

[Jannik Oberhagemann]

@Bill Sheboy Thanks for the answer. All I know is that "start date" is still flagged as essential and "due date" is not. I am unclear on how that happened or if that causes the problem in roadmaps. I was hoping someone knew a way to "relink" the field with the roadmap timeline. I will contact support and see what they suggest. 

[Giada Noè]

Hi @Jannik Oberhagemann, I think I have the same issue. Did you find a solution?
Thanks

[Jannik Oberhagemann]

Hi @Giada Noè it seems we have 2 different "Due Date" fields. One is the "correct" on and the other just a random custom field. The problem seemed to be, that the "correct" one only got listed in the field overview if you have your browser in English. If it is in e.g. German it just does not show up via the search function.

Hope that helps