Ankit

Hi @coltoneakins, Jira doesn't provide any API to clone the issue. So, the clone command is fetching and re-creating the issue with the most common fields. And, custom fields are...

> I would not consider it a breaking change when the CLI newly checks this. It merely points out an error situation that was previously wrongly ignored. I think we...

Hi @tarmotubro, based on the error message, it seems like your workflow doesn't allow to set `Priority` when creating the issue. Is that correct?

Hi @weshouman, there is `XDG_CONFIG_HOME` env available, wondering if that works for your usecase?

Hi @vyprabhu are you just running `jira issue edit --label "abc" --no-input` or you are streaming contents from stdin `echo "something" | jira issue edit --label "abc" --no-input`?

This only seem to happen in Jira Cloud

I think we don't support the item type of `checklist-item` (can't find it in [the docs](https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/#fieldformats)). We'd first need to figure out how the Jira is expecting the data to...

This actually looks like an issue with `init` command. Are you able to use `.netrc` after generating the config?

I meant if you can generate config using other methods (eg: setting `JIRA_API_TOKEN`) and then try to use `.netrc`, does it seem to work?

This seems to be working fine for me. The error `labels: Field 'labels' cannot be set. It is not on the appropriate screen, or unknown.` basically means your workflow doesn't...