Hi all,
I have created 2 workflows within a project. One for the Feature issue type, all unassigned issue types and other for dependency issue type.
The problem I'm facing is my create status is getting duplicated.
For example, by 1st workflow starts with New Request as status(Todo) for features and 2nd workflow should kick in for dependency creation with status as Discussed(todo)
But unfortunately what is happening is my 'New Request' status of 1st workflow is automatically getting renamed with 'Discussed status' which is part of 2nd workflow. So now I have kept 'new request' status as common for both workflow as a workaround..
I'm not sure if I'm doing some thing not with workflow logics..
Kindly assist.
Regards
Rahul Jith
Hi Rahul,
How is the second issue getting created? Are you using an Automation Rule or something else? If automation, can you post the rule?
Good day @John Funk
2nd issue is getting created manually only.
From the main feature, child issue created based on demand.. and for this child issue only 2nd flow is created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One more observation is this problem happens only if I'm creating a new workflow from the scratch. If I edit on an existing workflow to say default simple workflow as an example, it's not behaving like issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to clarify, no workflows are created based on an issue getting created. Workflows exist in the system already and are simply attached to an issue based on the issue type the workflow is attached to.
So, having said that, the workflow scheme on your project contains one or more workflows. If there are more than one, then all issue types on the project (i.e. in the Issue Type Scheme) are already attached to one and only one of those workflows.
If you have a story - then it is attached to a workflow. A sub-task may or may not be attached to a separate workflow. But just creating an issue does not create or alter a workflow in any way.
And, no, you cannot create a new simple workflow from scratch. Those are only created when brand new projects are created. If you create a workflow, it's just a workflow, but not a "simple" workflow.
Now, having said all of that. Can you describe in detail exactly what problem you are encountering? For example, when I create a sub-task from scratch, it is doing blah, blah, blah, and I want it to do this, this, this.
I hope that makes sense.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you paste a screen with second workflow? I am sure you have wrong configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good day @Damian Wodzinski ,
Yes I agree with you on my configuration. But I'm not able to find the route cause after weeks of troubleshooting and analysis.
Sure I will share the screen snaps of both 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.
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.