JMWE or some other tool: mandatory fields depending on the choice of single select field

[Jurica Petricevic]

Hello everyone,

I have the following problem not only when creating a ticket, but also when editing a ticket in the future after creating it.

Field 1 (single select field) has a minimum of four values, say A, B, C, D, E, and in case A, B or C is selected, Field 2 (Date field) must not be empty and must be filled with a date, and Field 3 (Text Field) must also not be empty. If the value D or E is selected, these two fields may be empty.

Is this possible to do?

Best regards

[Deleted user]

I'm having the same issue as described above my user as permissions in the UI but not via the api

[Claudiu Lionte]

Hi Huan,

When a user generates an API token at https://id.atlassian.com, any API calls made using that token will be treated as coming from that specific user. In other words, any script configured with that API token will run with the same permissions that the user has.

If the script attempts to perform an operation that the user does not have permission to perform, Jira returns a 401 error code (Unauthorized). This is expected behavior since this HTTP status describes the situation best.

If site access is disabled for a user any script / API calls running with an API token generated by that user will return a 401

The fact that a user can generate an API token even if site access has been disabled is related to the fact that a user can have access to multiple Jira sites and can use the same API token to send API calls to either of them.

[Huan Ting Chen]

If the script attempts to perform an operation that the user does not have permission to perform, Jira returns a 401 error code (Unauthorized).

If site access is disabled for a user any script / API calls running with an API token generated by that user will return a 401

These are not true. I can still get 200 even when a user doesn't have permission or access is disabled. I also figured out that an API token is still valid after I revoked it. I've tested the above on two different Jira sites and they behaved the same. Please can you advise?

[Claudiu Lionte]

Hi Huan,

I tried to replicate the behavior that you described but I couldn't. Please open a ticket at https://support.atlassian.com/contact and mention me, so we can take the discussion further privately, as I need some private information in order to investigate the behavior.

Claudiu

[Ivanov, Kyrylo [Global IT]]

I have created api token but got error

[Debug] [ Jira Webhook ] Received response with status code 404
{"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}

Issue exists and I have prmissions to read.