-
Suggestion
-
Resolution: Unresolved
-
27
-
As it stands right now, the only supported fields for displaying issues on the calendar or setting a timeline are start date and due date. I would like to be able to define different custom date fields to be used instead, for instance, onboarding/offboarding date
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JWMCLOUD-43] Ability to define different start date and due date fields on calendar/timeline views
Using Start and Due date for Non-engineering teams doesn't make sense! We need to use fields like - Go Live, Retract Promo. etc...
Additionally, in Plans, you can have warnings that react to both Target End and Due Date, so it seems there is validity elsewhere in the tool in allowing scheduling views to react to different dates.
This should be a priority! Already, there is a Content Calendar template in Jira, but it is hard to rely on Jira as a content calendar if we cannot easily see content publication dates in the Calendar view.
Please provide this feature since most of use other date fields in various project types!
Please don't stop progress on this. It's already available in JSM. And there is a real challenge across products now: JPD won't sync with Target Start and Target End, but Plans works well with comparing the end date with the due date, and Jira Timelines/Calendars only works with Start Date and Due Date.
It would help to have some guidance on what planning fields to use across all products, without using Due Date.