nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Recognizing an issue created from Slack /Jira Create

Adam Dulberg

Hello Community,

Until several months ago, upon "/jira create", a line was appended to the bottom of the description field "this issue has been submitted from /jira create" (or wording to that extent).

We could use that line to identify the ticket's source for rule creation/filtering. Since that text is removed, I'm unable to identify unique markers that tell me the issue was generated in Slack.

Does anyone know a way that identifies an issue was created by "/jira create"?

Accepted answers

David Michelson

Hi Adam,

After doing doing some testing of /jira create on my end, it seems to still be appending "Issue created in Slack using /jira create." to the bottom of issue descriptions.

Could you tell me the steps you went through to use /jira create and end up with an issue that did not have that appended in the description?

Where in Slack did you start? What sort of Jira project did you create the issue in? What sort of fields did you fill out?

Thanks

David - Product Manager

All comments

David Michelson

Hi Adam,

After doing doing some testing of /jira create on my end, it seems to still be appending "Issue created in Slack using /jira create." to the bottom of issue descriptions.

Could you tell me the steps you went through to use /jira create and end up with an issue that did not have that appended in the description?

Where in Slack did you start? What sort of Jira project did you create the issue in? What sort of fields did you fill out?

Thanks

David - Product Manager

Adam Dulberg

Hi David thanks for taking the time to look into the issue. I did a pretty exhaustive search of our instance and see that actually some issues do have it appended. There isn't workflow or automation removing it, must be something related to the field or how the issue is being created.

There are several moving pieces that is going to make this hard to describe, but knowing this is not being removed is enough to dive into.

I might be okay in the interim, thanks.

Adam Dulberg

Issue is much more obvious that I thought, very much a false alarm here. The issue is "Description" was not on the create screen for the areas it wasn't showing up. That is where it defaults to append....solution is put description on create screen and poof. Answer was in my initial post...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud