Hi Team,
We're using the classic jira project. In our epics we've two fields start date and due date.
Roadmap is using these two fields to represent. But when we updated these fields it's not reflected in the roadmap.
It's showing the bar line for old start and due date.
Can you please let us know where we're missing to show the updated start and due dates in roadmap?
Let us know if you need any more info. Thank you in advance.
Regards,
Narendra
How did you create "lipe-workflow"? It sounds like you've actually created a draft of ML1.2 and not copied it to a new workflow.
Start with the basics to get this fixed. Look at the list of workflows you have. Then look at the workflow-schemes you have for the projects. There should be a scheme for Lipe projects and another scheme for mL1.2 projects.
(The workflow change date represents your last edit to that workflow)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would be polite to mark the correct answer as correct. Or, if it wasn't that, then explain what the actual problem was.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same way you marked your own answer correct - the tick to the left of the avatar.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, I was editing workflow and creating new step and one new status. And I managed to create new workflow, but somehow I managed to change existing status to new (Instead of creating new status) :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know, it's a bit of a pain. Older versions of Jira didn't have the workflow designer, so it was hard to make this mistake, but the newer versions have enabled you to amend the global lists without realising that they're global. Easy to undo of course, but still a bit of a pain when you're new to hacking workflows.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Problem solved: "Linked status" (which is global) was changed -> this cause the problem. We changed the status as it was and now works again :)
Lesson was: should be very carefull which parameter is global and which is per project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahh, you changed the status, not the workflows. Right.
Generally, watch out for status and screens - as you've found, the workflows refer to these, but they're taken from a global list
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.