-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
2
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Hi,
We are the organization that has strict appointments with our customers. Our PM's do the planning in the Planner and then tasks are being executed by the field personnel who operates with the Kanban board of Jira Agile. When planner optimizes the tasks it works out optimal way of combining the tasks together based upon their priority and desirable start dates and values of start and stop are being generated. I think it will be wise to give these values some availability in JQL so the Kanbn can be generated.
Regards
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25031] Jira portfolio Start and end dates value availability in JQL
Andrew Whitley
added a comment - While having the dates available in JQL would be great so we can create email subscriptions for when tickets are not going to be completed on time, our organization would benefit most from having Scheduled Start and Scheduled End available via the api. This way we can have these dates in eazyBi to do some reporting on them. The only reason eazyBi does not have these fields as they cannot get them via the api.
We would like to create a roadmap report that shows a comparison between the target dates, scheduled dates, original and remaining estimate, time spent, original story points, and story points. This report would show us if tickets are behind, not scheduled, not being worked on yet, or on schedule/ahead. While a basic view of this is available in the portfolio scope view, it does not clearly give all of this information in the gantt chart so we would like a more customized report. We have a few other reports that would benefit from this information being made available so it would be appreciated if the scheduled dates could be made available.
Andrew Whitley
added a comment - While having the dates available in JQL would be great so we can create email subscriptions for when tickets are not going to be completed on time, our organization would benefit most from having Scheduled Start and Scheduled End available via the api. This way we can have these dates in eazyBi to do some reporting on them. The only reason eazyBi does not have these fields as they cannot get them via the api.
We would like to create a roadmap report that shows a comparison between the target dates, scheduled dates, original and remaining estimate, time spent, original story points, and story points. This report would show us if tickets are behind, not scheduled, not being worked on yet, or on schedule/ahead. While a basic view of this is available in the portfolio scope view, it does not clearly give all of this information in the gantt chart so we would like a more customized report. We have a few other reports that would benefit from this information being made available so it would be appreciated if the scheduled dates could be made available.
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC