-
Suggestion
-
Resolution: Low Engagement
-
None
Looking for a triggered event to clear the Start & End dates when an issue is removed from a plan. A Very Common Scenario: If a Program Manager has a pivot in their Tetris planning and decided they need to remove items from their Tetris board... they can then select one or more issues and perform "Bulk action" to "Remove from plan", then there should be an immediate triggered action to remove any values from the Target Start and Target End fields.
This is important because we will be running queries on existing Portfolio Plans based on filled in Target dates... this will be part of the various imports we will be used for scheduling and resource management. It is vital we are not pulling in issues into our queries that are not on Portfolio Plans but are showing up because they have fields filled for Target Start / End. The route of asking Program Managers to delete Target dates prior to removing them from Plans is less than ideal and would impact adoptability.
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25289] Looking for a triggered event to clear the Start & End dates when an issue is removed from a plan.
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
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center