How to automatically populate the values of the Custom fields at the Sizing Sub-Task level when ever we select the Component "Test Support Only" in the Epic ?

[Dinesh Loyapalli]

We have 2 post functions at the Sizing Story Create Transition which are used to create the Sizing Sub-Task.

Regardless of whichever component we select there is a Tech-lead Sizing Sub-Task that is created at the Sizing Story level. Now When ever we select the Component "Test Support Only" at the Epic Level this Tech Lead Sub-Task has to populate some default values in the Custom Fields present in it and the status of this Sub-Task should be Done Can this be Achieved ?

[Dinesh Loyapalli]

For ur information, We re-Implemented the Logic for creating the Sizing Stories and Component Stories at the EPIC Level..These post functions are present at Sizing story...

i would like to re-implement the logic for creating Tech-lead Sizing Sub-Task at the Sizing Story Create Transition using JWT...and then add the functionality that i have specified above...

[Fidel Castro Armario]

Hi @DineshLoyapalli,

You can implement the creation of Tech-lead Sizing Sub-Task using "Create issues and subtasks" at Sizing Storie's Create Issue transition with the following configuration:

String expression for setting field Issue status is:

"Test Support Only" in fieldValue(%{00094}, linkedIssues("has Epic")) ? "Done" : ""

where %{00094} is field code for Components.

I have added an example explaining how to set a certain custom field called Short Text with a specific value when Epic contains component "Test Support Only". The expression used is similar to the one for setting Issue Status:

"Test Support Only" in fieldValue(%{00094}, linkedIssues("has Epic")) ? "Value when 'Test Support Only' is selected in Epic" : ""

In order to move issue to Done status, a transition should exist from initial status to Done status, and their conditions and validators should be satisfied. JWT uses that transition to move the issue automatically to Done status.

[Dinesh Loyapalli]

The custom fields that i would like to set are Number Fields...For the value type i don't see any Parsed Text for these Number Fields instead i see Math/Time expression and i have set it to "80" .Will this work?

And also i don't have any Story link field to set up

[Fidel Castro Armario]

Yes, you should use Math/Time expression, but you should write the value without double quotes, and the alternative value will be null, i.e., something like:

"Test Support Only" in fieldValue(%{00094}, linkedIssues("has Epic")) ? 80 : null

[Dinesh Loyapalli]

This is the post function that i have added..Its creating the Tech Lead Sizing Sub-Task but its not changing the status to Done when ever we are selecting Test Support only in the Epic and also not populating the Custom fields with the values that i have specified above.I have added a transition from Open to Done In the Sizing Sub-Task Workflow.

[Fidel Castro Armario]

Hi Dinesh,

Try the following text expression:

"Test Support Only" in first(fieldValue(%{00094}, linkedIssues("has Epic"))) ? "Done" : ""

and the following math expression:

"Test Support Only" in first(fieldValue(%{00094}, linkedIssues("has Epic"))) ? 80 : null

BTW, you can hide your transition from Open to Done to users by adding condition "Transition is triggered by JIRA Workflow Toolbox post-function".

[Dinesh Loyapalli]

Thank you Fidel its working..

[Fidel Castro Armario]

You are welcome

[Dinesh Loyapalli]

Fidel,

"Test Support Only" in first(fieldValue(%{00094}, linkedIssues("has Epic"))) ? "Done" : ""

this expression sometimes working fine and sometimes its not changing the status.Just now i created a new issue and selected the component "Test Support Only" In Epic and did Impact Analysis,its created the Tech Lead Sizing sub-task but the status has not been changed to "Done"..and also it didn't populate the custom fields with the values that i have set.

[Dinesh Loyapalli]

Here is the post function that we have configured for creating the Tech Lead sizing Sub-Task:-

[Fidel Castro Armario]

Hi @DineshLoyapalli,

I don't find any problem with that configuration.

Can you, please, share with me your server's log file? Maybe there is some clues there. You can send it to [e-mail].

Please, attach to the issue, an XML export of the workflow. I would also like to see all the post-functions, conditions and validators in the workflow.

[Dinesh Loyapalli]

I cannot send an email out of my office network.But i have attached an XML export of the workflow.

[Fidel Castro Armario]

You can also attach the log file to the issue.

[Dinesh Loyapalli]

Now i have deleted the Sizing story that is related to Epic, again selected Test Support only Component and did impact analysis.Now it has changed the status of the TechLead Sub-Task to "done".But when i am creating the issue for the first and doing the impact analysis its not changing the status.

[Dinesh Loyapalli]

Hi,

Did you see any problem in this?

[Fidel Castro Armario]

Hi @DineshLoyapalli,

Can we have a screen-share through Skype? I would like to see the problem in direct.

My Skype user is fidel100r.

[Fidel Castro Armario]

Hi @DineshLoyapalli,

Any update on this issue?

[Dinesh Loyapalli]

Fidel,

Its still the same..When ever i create the new issue for the first time and select "Test Support Only" and do impact analysis, Sizing story is created and also Tech-Lead Sizing Sub-task is also being created inside the Sizing Story...But the status of the Tech-Lead Sizing Sub-task is in open Status...

Now i have deleted the Sizing story that is related to Epic, again selected Test Support only Component and did impact analysis.Now it has changed the status of the Tech-lead Sub-Task to "done".But when i am creating the issue for the first and doing the impact analysis its not changing the status.

[Fidel Castro Armario]

Hi @DineshLoyapalli,

Can we have a screen-share through Skype? I would like to see the problem in direct.

My Skype user is fidel100r.

[Dinesh Loyapalli]

I don't have Skype installed in my office system.We can have a screen-share through Zoom.Can you please mention the time-frame.I am available after 6:00 PM CST and 6:00 am to 8:00 am CST any day.Here is the Invitation:-

Hi there,

Dinesh Loyapalli is inviting you to a scheduled Zoom meeting.

Topic: Dinesh Loyapalli's Personal Meeting Room

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/9787531450

Or iPhone one-tap (US Toll): [phone],,9787531450# or [phone],,9787531450#

Or Telephone: Dial: [phone] (US Toll) or [phone] (US Toll) Meeting ID: 978 753 1450 International numbers available: https://zoom.us/zoomconference?m=BYAWFRq8WZr9KdyuosN6ezaru2VjwqWl

[Fidel Castro Armario]

Ok, I will be available tomorrow from 6:00 AM to 8:00 AM CST, i.e., 13:00 - 15:00 CEST.

[Dinesh Loyapalli]

okay.Talk to you tomorrow.

Thanks..

[Dinesh Loyapalli]

Just comment here when you ready to connect..

[Dinesh Loyapalli]

Hi Fidel,

Can we connect now?

[Fidel Castro Armario]

Yes. I'm ready

[Fidel Castro Armario]

The problem is solved simply by replacing term "Test Support Only" in first(fieldValue(%{00094}, linkedIssues("has Epic"))) with term "Test Support Only" in %{00094} in the post-function for creating Tech Lead sizing sub-task in the Story workflow.

With this solution the Tech Lead sizing sub-task will be automatically transitioned to Done status when Sizing Story contains component Test Support Only among others, but if you want to transition when Test Support Only is the only component in the Sizing Story, then you should use the following term: "Test Support Only" = %{00094}.

[Dinesh Loyapalli]

replaced the term "Test Support Only" in first(fieldValue(%{00094}, linkedIssues("has Epic"))) with term "Test Support Only" in %{00094} Everything is working good.Thank you so much Fidel. Thanks for connecting and helping me out..

[Fidel Castro Armario]

You are welcome.