Issue #661 new

How not to create a component story and the sizing sub-task for a Specific Component?

Dinesh Loyapalli
created an issue

In the epic when ever we select the component a respective Component Story and Sizing-Sub task is created.Now we have added a new Component "Test Support Only".So when we select this component and do "Identify Impacts", it should not create any Component story and Sizing Sub-task.Can this be achieved?

Comments (19)

  1. Fidel Castro Armario repo owner

    Sorry, Dinesh, I don't understand what you intend to do. I assumed that you wanted to create a Component Story for each component selected in the Epic issue.

    BTW, please, I can't see the whole value of some parameters in screenshot 'Epic Impact Analysis Post Functions2'.

    Are those 3 post-functions in transition Impact Analysis?

  2. Dinesh Loyapalli reporter

    Only for the component "Test Support Only" which we have added recently, it should not create a Component story and the respective sizing sub-task..For all the remaining components we will use the functionality that we have implemented in our previous sessions.

  3. Dinesh Loyapalli reporter

    Instead when ever we select the "Test Support Only" Component it should create a tech lead Sizing sub-task inside the Sizing Story and the summary of it should be "Tech Leads Sizing" for "Parent Summary" and should populate some default values in the Custom fields present at the Sub-task level.

    Custom Fields that were present in the Sizing Sub-Task is:-

    Initial Planning/Partner Engagement: 10
    Initial Analysis: 10 Initial Design: 10 Initial Build: 10 Initial IST: 10 Initial UAT: 10 Initial SPL: 10 Initial Deployment/Post Production: 10 Initial US Efforts: 80

    Planning/Partner Engagement: 10 Analysis: 10 Design: 10 Build: 10 IST: 10 UAT: 10 SPL: 10 Deployment/Post Production: 10 US Efforts: 80

    All these values should be rolled up and should be added at the Sizing Story level..........

  4. Fidel Castro Armario repo owner

    Try replacing term toStringList(%{00094}) with term toStringList(%{00094}) EXCEPT toStringList("Test Support Only") in string list expression for generating seed strings in post-function 3.

  5. Dinesh Loyapalli reporter

    Instead when ever we select the "Test Support Only" Component it should create Sizing sub-task inside the Sizing Story and the summary of it should be "Tech Leads Sizing" for "Parent Summary" and should populate some default values in the Custom fields present at the Sub-task level. Custom Fields that were present in the Sizing Sub-Task is:- Initial Planning/Partner Engagement: 10 Initial Analysis: 10 Initial Design: 10 Initial Build: 10 Initial IST: 10 Initial UAT: 10 Initial SPL: 10 Initial Deployment/Post Production: 10 Initial US Efforts: 80 Planning/Partner Engagement: 10 Analysis: 10 Design: 10 Build: 10 IST: 10 UAT: 10 SPL: 10 Deployment/Post Production: 10 US Efforts: 80 All these values should be rolled up and should be added at the Sizing Story level and the status of it should be Done Automatically.

  6. Dinesh Loyapalli reporter

    we are using create on transition for creating this Sizing sub-task at the create transition of the Sizing story .Here is the post function present in create transition of the Sizing story.:- Post Function.PNG I would like to implement the same functionality using JWT. Then implement the functionality that i have mentioned in above comment.

  7. Fidel Castro Armario repo owner

    Hi Dinesh Loyapalli,

    At the initial description of the issue you said "...it should not create any Component story and Sizing Sub-task.", and now you say "...it should create Sizing sub-task inside the Sizing Story...".

    Initially you attached a screenshot showing that Sizing sub-tasks are being created with Create issues and subtasks, but now you add another screenshot showing that Sizing sub-tasks are created by Create on transition add-on.

    Initially you also told me that you wanted to avoid the creation of Component story for component "Test Support Only", but the screenshot you attached initially shows that you are creating Component stories using Create on transition, which is a plugin that I don't support.

    The thing is that I think that I have already explained in previous issues how to create Component story and Sizing sub-task using Create issues and subtasks, and I don't understand why Create on transition keeps appearing. Maybe you are working with duplicated workflows. In that case, I recommend you to implement the solution I provide you in all your workflows, or try to reuse your workflows in order to reduce their number.

    Please, understand that for me is a big effort to support on such complex scenarios, and although we have talked about related scenarios in previous issues, I usually don't remember them. Providing a unique, consistent, clear and detailed description of the scenario will help me very much.

  8. Dinesh Loyapalli reporter

    The first screen shots i have attached were the post functions at the Epic level and the screen shots that i have attached in the above comment was at the sizing story level.

    Sorry for confusing you...i am new to Jira and all these add-ons.

  9. Dinesh Loyapalli reporter

    Regardless of which ever component we select A Tech lead sizing Sub-task is being created at the Sizing Story level.I didn't inform you about this because we have implemented this using different add-on.Now we are not able to create the Sub-task for the "Test Support Only" inside the sizing story based on the logic that you have mentioned above at the Epic Level.

    There is 1 more post function at the Sizing Story level which is used to create the Tech Lead Sizing Sub-Task.

  10. Fidel Castro Armario repo owner

    Sorry Dinesh Loyapalli, I think I have been a bit rude in my previous post. I think that trying to use an issue for each requirement will help to avoid confusion.

    Please, provide me the whole string list expression you are using for creating seed strings at "Create issues and subtasks" post-function for creating component's sizing sub-tasks at transition "Identify Impacts", since the screenshot you attached (Epic Impact Analysis Post Functions2.PNG) doesn't show the whole content.

    Please, provide the string list expression as text, not as an image.

  11. Dinesh Loyapalli reporter

    No you don't have to say sorry.... i know i am not able to explain clearly....I have made the changes that you have told me to do and its working fine.Now its not creating Test Support Only Component Sub-tasks

    String List expression:- filterByPredicate(toStringList(%{Components}) EXCEPT toStringList("Test Support Only"), count(filterByPredicate(subtasks(filterByIssueType(linkedIssues("is Epic of"), "Sizing Story")), ^%{Summary} ~ ^%)) = 0)

    "Create issues and subtasks" post-function for creating component's sizing sub-tasks at transition "Identify Impacts" is present at Epic level.

    Let me create another issue about the post functions present at the Sizing story level and we can take it forward from there.

  12. Fidel Castro Armario repo owner

    Ok, I think it's a good idea to use another issue for requirement at Sizing story level.

    Now, you keep having the problem that Component Story keeps being created for Test Support Only component. Isn't it?

    You are using Create on transition for creating Component Story, and I can't help you, unless you move to "Create issues and subtasks" post-function.

  13. Dinesh Loyapalli reporter

    yeah i know that a component story is created at the Epic level.We don't have to do anything with it.We only have to work around the Post function that is used to create a Sub-Task inside the Sizing Story which is not based on Components .

  14. Log in to comment