Our organisation has recently run into the "1000 sub-issues limit".
After looking for answers or details on this issue, I've been left guessing what it actually means or how I can resolve it.
I am currently managing a JDP board with 250 ideas that link to various different epics.
Only when an idea reaches a certain status (out of 7 statuses) will there be jira issues/epics linked to the delivery.
At the moment we have around 20 ideas with issues linked in delivery.
Once and idea is set to "Done" it is automatically archived.
Though even after archiving 4-5 ideas in the last week as a huge piece of work had finished, we started getting the warning as shown below.
Nothing seems to be broken at first sight, but I cannot find any information regarding the warning and don't know what the limitations are and what they may cause.
Hi @Jess Williamson , thanks for your question.
Please can you also share an anonymised version of the Rule details tab? The error message is saying the Actor doesn't have enough permission, so you need validate that here -
Then, please check the permissions for the project to ensure the rule Actor, whether this is Automation for Jira or a user, has the transition issues permission.
Hope this helps but if not, please write back and either I or someone else will try to help you.
Cheers
Thanks Valerie, I changed the Actor to myself and now it works.
Cheers!
Jess
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Jess Williamson , please consider accepting my answer so that it can help other users who might encounter the same issue.
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jess Williamson ,
Based on that error, the A4J user may not have permission to perform this action on JPD ideas. If @Valerie Knapp suggestion below does not resolve the issue, feel free to open a ticket with JPD support and we'll look into it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.