What is the challenge? |
We use a custom field called "target quarter" in which features are relegated to. Since I cannot select that field to anchor features to the columns, i can't add issues to the roadmap with this custom date field |
What is the impact? |
I cannot use the roadmap feature |
Describe your idea |
Enable a "custom" element in the drop down and allow users to parse on any date fields they may have for a ticket attribute |
I think the problem is more common than the votes give impression.
Creating a roadmap without dates but still based on the release dates makes no sense.
The idea of a custom field allows the release date to stay linked to the engineering release while postulating that there are target market dates.
To solve this problem, we have removed the JIRA integration link of the release date, but then we lose that piece of information when the release is made.