I want to count the status of a child issue close when it is deleted.

[koutarou ishibashi]

I may be wrong because I am not good at English.

JIRA Automation counts the number of child issues whose status is closed.
I set the trigger when creating a child issue and when transitioning a child issue.
I want to be able to run it when a child issue is deleted.

We currently have the following settings, but please lend us your wisdom so that it can be executed even when a child issue is deleted.

When: Manually triggered
All logged in users van run rule.

Then: Lookup issues
Search for issues using JQL
parent = {{issue}} and status = "Closed"

And;Edit issue fields
Word Count

[Deleted user]

Hi @Eric B,

Great in-depth problem you have presented and I am very happy to help where I can. I would like to clarify what you want to get out of both packages and how you would like them to integrate better? 

Can I assume you use MS Project to track the overarching life cycle of your projects / entire portfolio, whereas Jira is solely used to track tasks for your Project Team/s?

Have you looked into Portfolio for Jira?

Main features include;

• Capacity Planning
• Roadmap Scheduling
• Forecasting 
• Roll-up Reporting

I use Portfolio for Jira to bridge the gap between the granular task management and the entire project / portfolio management. Essentially offering some high level features that MS Project offers. 

Hope this helps  

[Eric B]

Thanks for the reply @[deleted]

Right now my dilemma is related to just 2 projects. I have all the IT tasks in JIRA and a set of spreadsheets used by the business that contains all their activity.

I am using MS Project for the overreaching view like you said, but not to a portfolio level. I am using it to produce basic project data that I am not getting from JIRA, to schedule the work, to provide a consolidated view of project work and to get visibility into overall progress.

Project is individually licensed copies on local machines. JIRA is the only tool that could give me any portfolio level visibility, but you can see how it is being used negates whatever value it could have there.

I finally got a schedule together yesterday that I think will be workable. Not good. It is full of lots of manually entered, unreliable data because of the spreadsheets and data that is not captured in JIRA. Workable though. Surprisingly it is improvement to what was going on before.

I will check out Portfolio today and see if I can bridge any gaps of my own.

Thanks for the recommendation!

[Deleted user]

Glad I could help @Eric B,

Let me know how it goes.