Hi,
I need to find the id or name of the screen associated with the specified issue. How to do that using the Jira CLI (https://bobswift.atlassian.net/wiki/spaces/JCLI/overview?homepageId=6684681) or REST API?
regards,
Darek
every issue belongs to an issue type and this has three possible screens - for viewing, editing and creating an issue. These 3 screens are assigned based on the issue type and the project.
In order to retrieve them via the REST API, you can call the following endpoints:
Hope this helps - it's unfortunately not such a straight-forward process. I've realized this while implementing our app Project Gardener.
Cheers,
Matthias.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thx Matthias,
You can see that my Jira is a Server version (see bottom-top corner) and it doesn't provide mentioned API in ver 3. It is available only for the Jira Cloud version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, I missed that part - my bad.
I believe for server, the other answer is correct that this isn't possible :/
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.
Hi @Dariusz PAWLAK ,
As it is not possible to get the screen associated with the specified issue using the CLI action. CLI works with the REST API provided by Atlassian.T
There is no REST API for the same
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if I know the IDs of: the issue, issue type, screenSchema associated with issue's project?
Is there any indirect way to get screen info?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then you are claiming that CLI adds nothing of value, which is incorrect on the very base level.
The plugin can implement it's own getters and methods to get anything it wants, and expose an interface to do it. That is the fundamental reason why it can do something the out of box REST API cannot - because they create their own endpoints to do various stuff.
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.