Different managers for the same slack workflow see different fields for 'create a JIRA issue' step

[Bhargavi Deshpande]

So we have this slack workflow to create JIRA issues under a specific EPIC. It was not working for my colleague - it would not create the JIRA task and hence fail. When he added me as a collaborator - I could not see any of the custom fields as the person who originally created this workflow. It looked like this for me

 

and looks something like this for my colleague who created the workflow 

Hence I was able to publish the exact copy of the workflow and run it but my colleague could not because he had to fill in something for reporter (mandatory field for him, not showing up as a field for me) which blocked the creation of JIRA task which is not editable due to this.

So my workflow worked for both of us when triggered but not his.

Do we know why the same workflow showed different fields for him and me?

[Alastair Wilkinson]

I would guess this is tied to the underlying Jira project permissions that you are connecting  to and perhaps different project roles between you and your colleague. Are any of the custom fields restricted or have permissions around which roles can set/change them?

[Bhargavi Deshpande]

Yes, but if anything the JIRA project is administrated by my colleague whereas I have very limited access to that JIRA project. Does that impact which fields pop up under additional inputs in the 'create JIRA issue' in the slack workflow?

   

[Bhargavi Deshpande]

.