Tracking outcomes and impact of released features

[Boleslaw Nowak]

Hello!

Trying to figure out a solution for monitoring of the released features that we release every week, and thought I'd ask for advices and how do you work with those.

As of current we do it quite manually which has its obvious flaws, with the biggest one being hard to maintain, and read - as it just grows to a gigantic Confluence table.

Wondering if you have any good patterns within Jira that serves this purpose of monitoring of the tasks - for 3-4-5-6months to evaluate the tickets impact, or any other good tips that work for you.

Currently my only idea is to make a board and filter the `Released` tickets by some kind of a label, and then work from there, but this doesn't sound like a perfect solution.

Cheers!

[Alexey Matveev]

Hello,

You would need an add-on for it. For example, you could use the Power Scripts add-on:

https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview

You could create a post function with a code like this:

#{Field A} = #{Field B} - #{Field B} * 0.3

 You can read more about post functions here:

https://confluence.cprime.io/display/JJUPIN/Customizing+workflows