My requirement is to create a new issue and automatically change the status of the linked issue .
Two projects are there . project a ,project b .
in project a i am creating an issue .
status transitions . pending --> allocated --> fix provided -->fix sent --> move to production -->deployed in primary customer
when i changed from fix sent to move to production state then the new issue will be created in the project b .
once the issue created in the project b, then i tried to change the status of issue which is created automatically in that transition .
for the project b i am using some different workflow .
pending --> in progress --> deployed in primary customer -->Closed
in this when i changing the status from in progress to deployed in primary customer in the project b , then in the project a issues which is linked with the tat issue in the status of move to production will gets changed automatically to deployed in primary customer status in the project a issue .
if possible please guide me for this .
i have used the link type in the project a where the issue is creating automatically as below .
but it is not working for me .
project a auto creation of issue.pngproject b auto issue status changing.png
Post-function "Write field on linked issues or subtasks" should be inserted in workflow of project B, in transition from In Progress to Deployed In Primary Customer.
Virtual field Target status is available since version 2.2.26. If you are using an earlier version I recommend you to update to the most recent version of the plugin. Anyway, you can also use the following configuration instead:
Hi Fidel ,
Thanks for the reply .
Its working fine now .
I have some doubt with this .
When i try to create a post function write field on linked issues or subtasks ,
there is a field in the name of :Filtering linked issues or subtasks by status:
This field is representing the status of the linked issue which is in the current status or the status which needs to be changed in the current transition .
And shall i choose the source value type as field in the current issue (issue status)
|Target field to be written in linked issues or subtasks|
as issue status .
if i am choosing only the issue status then the status of the issue only will affect ??.
if i choose the execute the transition that will also change the status and additional post functions mentioned in that transitions ???
i have updated the version to 2.28 of workflow toolbox .
If you are not getting my point please let me know .
All the filtering parameters (including "Filtering linked issues or subtasks by status") refer to issues whose target field is going to be set (i.e., linked issues and/or sub-task).
In order to transition other issues, you should write into any of the following 4 virtual fields:
So when using "Write field on linked issues or subtasks" to transition other issues, we have to select as Target field any of those 4 virtual fields, and select as source value a status name or a transition name depending on the specific target field we have selected.
In parameter "Filtering linked issues or subtasks by status" you should select the current status of the issues you want to transition, i.e., the status before being transitioned by the post-function.
Please, let me know if you have any other doubt.
Yah i understood it now .My doubts are cleared .
I am Having a new requirement as follows .
we are tracking the customer support issues with the help of JIRA .
For that we are creating two projects for a single customer with the name like
customer name - customer (project 1)
customer name - internal (project 2)
at present we are using the same workflows for both projects and also for all customers .
when the customer creates the tickets in the customer project at the same the issue needs to be created in the internal project also .
when internal people changing the status in the internal projects will it reflect with the related customer projects ...
i can create two workflows that is for internal as seperate and customer for seperate .
when customer a creates the issue in project aa that automatically creates into project ab
when customer b creates the issue in project ba that will automatically creates into project bb .
is it possible only with two workflows for all customer projects ???
if you cant able to understand please let us know .
Yes, it can also be done using a single workflow, but I think you may prefer using 2 different workflows in order to be able to tweak each project workflow separately. Tell me your preference.
I think this issue has enough entity to be treated in a separated question. Do you mind creating a new question? Please, add the following labels so that I will be notified when it's created:
I assume that you are not having problems creating Incident issue using "Create issues and subtasks" post-function.
I think that the problem is that you are using as source value in "Write field on linked issues or subtasks" post-function the current status of the Incident, which still is In Progress at the moment of the execution of the post-function.
Please, try the following modifications in post-function "Write field on linked issues or subtasks" in transition from In Progress to Deployed In Primary Customer statuses in Incident's workflow:
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs