I created a transition post processing rule to update an issue's Start Date to the Current date and time when the issue is transitioned to In Progress. I have verified that this works and can see the current start date in the issue. When I view that issue in my plan that has a field column to display the start date, I don't see the date in the field or in the schedule. I have verified that the correct field ID of the start date is being used in the scheduling.
However, I can set the start date of the issue by picking the date in the start date column in the Plan View and it will display in the column and in the plan.
What am I missing? Thanks in advance!
I'm having a very similar (or identical?) problem. When you set the Start date from the Plan View and save changes, is it still visible in the Plan View afterwards? For me it disappears from the Plan View even when set from there and but the new Start date *is* visible from the Issue View.
Edit: Another oddity is that in Scheduling while End date immediately shows Due date when the page loads, it takes a few seconds before Start date is populated with the expected field.
I realized the cause of my issue: the start field in question was of type datetime rather than datepicker - still can populate with a calendar but seemingly unsupported by Plans. Changed to a datepicker field and works as expected now setting from either the Issue view or Plan view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dan Spearing Welcome to the community!
Could you please check the Start Date field on the Automation and the Start date on the Jira plan match?
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I changed the Start Date in a Workflow Transition. Is there a way to check it there? There are 2 listed in the dropdown list of the Update Custom Field Post Function. I tried both.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you try to inspect the page and find the customfield ID?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Custom ID in the issue that I set in the transition is 10241. Verified using the inspector.
In that Plan Settings, under the Date:
"Choose which date fields to use when visualizing work on the timeline."
Start date
Start date (id: 10241)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you try adding both date fields to your plan and your workflow, to see if the other one gets populated, coz this is weird.
If you make the update on a workflow transition or directly on the issue view by editing the field value, it should propagate to the plan immediately.
If you make the change on Jira plan, you need to save the changes to the issues, only then the changes will be reflecting on the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Added both Start dates to the plan and neither show the start date that was set inside the issue directly.
I did try sourcing a different project and a start date did show up at the Epic level only. The start dates are not set in the Epic or any of its child issues. However, there is Time Worked that was recorded on some of the child tasks. The Epic has a start date showing in the Plan but the child tasks that actually have the recorded time worked within them don't show a start date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.