nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Listener for existing issues without opening each issue

Michael Preiss

Hi,

I have implemented my first listener within an existing project (approx. 400 issues). I want to fire the listener (which calculates couple of custom fields) without the need to open each issue. What is the event to use? I implemented "issue created" and "issue updated" event but this only fires listener for created or updated issues and not all issues in my project, of course. Can anyone help a bloody beginner?

Accepted answers

All comments

Martin Bayer _MoroSystems_ s_r_o__

Hi @Michael Preiss welcome at the community.

The idea of listeners is to listen to events raised by SOME object (issue, project, authentication module....), so it will never cover ALL the objects. It also would not be smart because in case of a large number of objects it definitely could have peerformance impact.

So you have to use listener just to be notified that "something happened" and do the rest on your own. If you will describe your use case in detail, we can design the solution together (if it is not some rocky science )

Michael Preiss

Hi Martin, many thanks for replying.

Some more information:

I have a running project with approx. 400 items. Now I need to define a new custom field (a KPI) that needs to be calculated based on input of existing custom field. I have wrote the code for the listener. Now I need kind of a bulk update - so that all custom fields (again approx. 400) are calculated. Otherwise and due to the event trigger "issue updated", i would have to open each single issue manually. So I somehow need to fire the listener for all issues within the project. Can you help?

Michael

Michael Preiss

Hi, in future the trigger "issues updated" is perfectly fine but I need to do an initial bulk update so that all issues have this calculated field value.

Martin Bayer _MoroSystems_ s_r_o__

ok I can see the multiple ways

write a script and run it in ScriptRunenr's Script Console. You would need to add part which selects required issues by JQL and call your function for all the issues
add self transition (transition from Any to Itself) and add your code as postfunction to it. Then you can use Bulk operation Move to invoke this transition which will recalculate value
I'm thinking about simple one and hope it will work. Invoke Edit operation in bulk and updaate some unimportant field. ISSUE_UPDATED should be triggered. If there is no unimportant field you can create one for this purpose and remove it after KPI is calculated.

Let me know if you need additional help

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server