Ankit

Hi @JoMetso, I remember facing the same issue and I think this should already be fixed (can't find the commit tho). Could you please try with the recent build? Thanks!

Looks like the issue is when using `--no-input` parameter?

@JoMetso @fishhead108 This should be fixed with #728 and will be included in the next release. Let me know if you still have issue with this.

Hi @masukomi, I am also using jira-cli with SSO in my company but its a self-hosted Jira Server. I think it should work if are able to generate Personal Access...

@comjf / @spprashant are you using local Jira installation? The token generated in local installation is used with basic auth IIRC so we don't need to set `JIRA_AUTH_TYPE` to `bearer`.

Closing as this seems to be system dependent and out of scope of this project.

That's strange! It looks like the API is not returning [Assignee field](https://github.com/ankitpokhrel/jira-cli/blob/ed84fe74f68ba1b2cf0504a931ca09a03b2c9fed/internal/view/issue.go#LL203C35-L203C35). I cannot reproduce this behavior in `8.22.2`, are you able to add assignee from the UI? Also, could...

@XVilka This looks something specific to your installation, are you able to set assignee from the UI? Also wondering if the problem is only with that particular field or other...

Hi @csamcharles, I believe your instance is returning a HTML response because of some error (probably 404). Could you please check which endpoint is failing with `jira issue list -a$(jira...

@aes256Slater This is a `Multi-user picker custom field` which is not supported at the moment as mentioned in [the docs](https://github.com/ankitpokhrel/jira-cli/discussions/346). I will see if I can add this quickly.