How can I transition an issue if a reporter/creator is part of an organization (any organization)?

[Nathan Given]

I'm using Automation for Jira and I was hoping to be able to look at all newly created issues, and if the reporter is part of any organization, transition that issue to a different status.

I can't seem to figure it out, though, with the conditions available to me (I have a huge list of organizations and I don't want to enumerate them all in the condition settings... thus I just want to see if the reporter/creator/customer is part of any organization (it doesn't matter which one) and then transition the issue to a different status.

Thank you,

Nathan

(This is for a Jira Service Desk project and I'm using the customer organization capabilities

[Iago Docando]

Meanwhile, you could use the "user is in group" condition as a workaround. 

If I understand correctly you want one workflow for users with no organization and another one for users from any organization.

You could create a wokflow combining those two workflows you want and simply add two transitions right after issue creation, each transittion pointing to the start point of each workflow. You could show/hide those transitions using that "user is in group" condition.

Things to keep in mind with this approach... Watch any transittion that can be triggered from any status because that would bypass the initial filter. You'll need to avoid those.

Maybe you can use a plugin like https://marketplace.atlassian.com/apps/1218266/csv-user-importer-for-jira?hosting=datacenter&tab=overview to bulk edit your users and add everyone that belongs to any organization to this new group. To my knowledge there are some plugins out there that allow you to bulk edit users but I haven't used any of them myself.

Hope it helps. It's the only workaround that comes to mind

[Scott Harwood]

Hi Nathan,

Unfortunately not. The problem is that there is no Service Desk APIs at the moment to check this in a performant way. We would need to iterate through every organization on the instance, and all of its users in order to match it to the user. 

We hope in the future that an API will be released that will allow us to support this.

Sorry,
Scott.