Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How i could customize Create issue from slack message popup

Kamil Dobrzyński
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 3, 2023

We would like to customize and disable many optional fields that are presented when using Create issue from slack message feature. 
How we could configure it to not show this fields inside popup? 

 

It's especially important and blocker for using of Product Discovery tool from Atlassian.

Screenshot 2023-08-03 at 13.22.28.png  

1 answer

0 votes
Bob Kleinberg August 3, 2023

Kamil,

When I use "Create Jira issue from Slack", my popup usually starts with: asking Project (red arrow) and Issue type (green arrow):


Screenshot 2023-08-03 085753.png

When you choose the issue type, it determines the list of fields to display.   So if you want fewer fields to display, you have two choices (as far as I can tell):
(1) For the specific issue type that is being used in your "Create issue in Jira" Slack action, create an alternative Create screen for that issue type that has fewer fields.  Then that is what will appear from Slack's create issue screen.  However, that also means that the Jira "Create" button will also only show that reduced set of fields.  The other fields will be there in the View/edit screens, but not in the Create screen.  OR
(2) Create a new issue type that has the smaller number of fields that you want to available when creating an issue from Slack.  Associate that with the project.  Then, when you "Create issue in Jira" from Slack, use that new, reduced field issue type.  However, you'll probably want to follow that up with set of automation tasks that create a new issue (of the original type), copy the fields you populated with the reduced field issue type, and then close out the reduced field issue (Status = Done, Resolved  = Done or copied, or whatever), so you are not tracking this new reduced issue type in your Kanban, Sprints, etc.  
Of the two, I would opt for the first one, especially if under normal Create circumstances you really only want a subset anyway.

Bob

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events