No me aparecen los campos configurados en Create Screen

[Karen Caramelo Alves]

Tenemos una configuración de campos configurada para que a la hora de crear un issue nos pida determinada información, pero desde ayer esta info que aparece en la pantalla es errónea. Por ejemplo, tenemos obligatorio poner un Parent en el issue. Está configurado así, pero en ningún momento se muestra el campo en la pantalla al crear el issue.

[Fabio Racobaldo _Catworkx_]

Hi @Karen Caramelo Alves ,

first of all try to check if you hide some fields from screen https://support.atlassian.com/jira/kb/users-dont-see-some-fields-when-creating-jira-issues/ 

If all is ok on your side, please contact a Jira Admin in order to check create screen. 

Hope this helps,

Fabio

[Karen Caramelo Alves]

Hi Fabio!

Fields are not hidden. Also, I've checked the Create Screen and everything is correct.

We've realised this only happens to one person so far. We are both Site Admins, I can create the issue without any problem, but he can't. We haven't found anyone else experiencing the same problem in the organisation. Could it be a consequence of yesterday's incidence?

Thanks for your help!

Karen

[Gor Greyan]

Hi @Karen Caramelo Alves

If this was working previously and has stopped only recently, I'd first verify that the Create Screen and Field Configuration are still configured correctly for the affected issue type.

Just to clarify, is this a Company-managed project or a Team-managed project?

[Karen Caramelo Alves]

Hi Gor,

Thanks for your help.

Indeed, this was working before, and the configuration hasn't been modified.

We've realised this only happens to one person so far. We are both Site Admins, I can create the issue without any problem, but he can't. We haven't found anyone else experiencing the same problem in the organisation. We cannot find what's causing this either.

Karen

[Gor Greyan]

Hi @Karen Caramelo Alves

Since it only affects one user while another Site Admin can create issues without any problems, it doesn't appear to be a configuration issue.

I'd first ask the affected user to try an incognito/private browser window or a different browser. If the behavior is the same, it would also be interesting to know whether it happens in all projects or only in this particular one.

If it's limited to a single user across all projects, it points more toward an account-specific issue, in which case I'd recommend raising a support ticket with Atlassian.