Ankit

@danmichaelo I was not able to reproduce it _fully_ (the behavior was bit unpredictable in my setup 🤷‍♂️). I made some adjustments based on a hunch though. Could you please...

@danmichaelo Sorry I forgot to mention that you need to re-generate the config (`jira init`). Also, could you please try it with the configured project (without `-p`). Using `-p` option...

@danmichaelo Unfortunately I am not able to replicate this in my setup. But looking at your message it seems like the generated config is missing some data. Could you please...

Hi @hugoamvieira, to confirm you are using `next-gen` project and not `classic` right?

Are you able to set epic using [jira epic add](https://github.com/ankitpokhrel/jira-cli#add-1)? Attaching issue on creation seem to be working fine in my setup (cloud) so I might need some extra details...

@hugoamvieira this can only happen if the config doesn't have value for `epic.link`. Could you please check and confirm that the generated config file has valid value for `epic` section?...

`epic.link` is a custom field and is populated using [/rest/api/2/issue/createmeta ](https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-createmeta-get)endpoint. It would be helpful If you can execute following curl command and see if the API returns `Epic Link`...

@hugoamvieira its strange that the response doesn't have "Epic Link" field for issue type "Epic". Does the issue link on create work if you manually add `customfield_10008` to `epic.link` ?

PR would be nice :)

Most of the terminal discovery is being done by [rivo/tview](https://github.com/rivo/tview) (for tui) and [charmbracelet/glamour](https://github.com/charmbracelet/glamour) (for issue view). > Do you have --plain printing isolated to a certain place in the...