-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Problem Definition
Currently, the /jira create command lacks the functionality to allow users to customize which fields are to be filled out during the issue creation process. This limitation arises from Slack's restrictions on the maximum number of fields that can be displayed within the issue creation modal. Efforts are made to select fields relevant to the project and issue type chosen by the user, yet it may not always be feasible to display all available fields for the specified issue types due to these Slack constraints. In such instances, users are presented with a warning message and advised to create the issue directly in Jira should they need to complete those fields.
As of now, the customization of fields displayed in the Slack 'Create Issue' form is governed by the fields configured in the 'Create Issue' screen for the respective issue type in Jira Cloud. It is important to note that any modifications to this screen, whether adding or removing fields, don't instantly reflect in Slack. There could be a delay before the changes in the field configuration are visible in Slack's issue creation process.
Suggested Solution
It would be beneficial to have a feature that allows configuring the form for the /jira create command on a per-project and per-channel basis.
Why this is important
By implementing this feature, issues created in Jira via Slack would be fully detailed from the outset, eliminating the need to edit the issue post-creation to add additional information not available on the Slack creation form.
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
[API-157] Customize the fields in the 'Create Issue' form in Slack
| Remote Link | New: This issue links to "Page (Confluence)" [ 1025193 ] |
| Description |
Original:
h3. Problem Definition
At this moment, the {{/jira create}} command doesn't have the option to customize which fields will be filled during the creation of the issue. This happens because slack has some restrictions on the number of fields that can be displayed on the {{create issue modal}} . We do try to fetch the fields based on the {{project}} and the {{issueType}} selected by the user but we may not be able to show all the available fields for the given {{issueTypes}} due to slack restrictions. In that case , we show the user a warning message and ask them to create the issue from jira if they still need to fill in those fields. h3. Suggested Solution Would be useful if there was a way to set the form from the {{/jira create}} per project per channel h3. Why this is important That way, the issue created in Jira, through Slack, would be completed filled, not needing to enter the issue after its creation to provide more information not available in the creation from on Slack |
New:
h3. Problem Definition
Currently, the /jira create command lacks the functionality to allow users to customize which fields are to be filled out during the issue creation process. This limitation arises from Slack's restrictions on the maximum number of fields that can be displayed within the issue creation modal. Efforts are made to select fields relevant to the project and issue type chosen by the user, yet it may not always be feasible to display all available fields for the specified issue types due to these Slack constraints. In such instances, users are presented with a warning message and advised to create the issue directly in Jira should they need to complete those fields. As of now, the customization of fields displayed in the Slack 'Create Issue' form is governed by the fields configured in the 'Create Issue' screen for the respective issue type in Jira Cloud. It is important to note that any modifications to this screen, whether adding or removing fields, don't instantly reflect in Slack. There could be a delay before the changes in the field configuration are visible in Slack's issue creation process. h3. Suggested Solution It would be beneficial to have a feature that allows configuring the form for the /jira create command on a per-project and per-channel basis. h3. Why this is important By implementing this feature, issues created in Jira via Slack would be fully detailed from the outset, eliminating the need to edit the issue post-creation to add additional information not available on the Slack creation form. |
| Summary | Original: Customize the fields from the create issue from Slack to Jira | New: Customize the fields in the 'Create Issue' form in Slack |
| Description |
Original:
h3. Problem Definition
At this moment, the {{/jira create}} command doesn't have the option to customize which fields will be filled during the creation of the issue. h3. Suggested Solution Would be useful if there was a way to set the form from the {{/jira create}} per project per channel h3. Why this is important That way, the issue created in Jira, through Slack, would be completed filled, not needing to enter the issue after its creation to provide more information not available in the creation from on Slack |
New:
h3. Problem Definition
At this moment, the {{/jira create}} command doesn't have the option to customize which fields will be filled during the creation of the issue. This happens because slack has some restrictions on the number of fields that can be displayed on the {{create issue modal}} . We do try to fetch the fields based on the {{project}} and the {{issueType}} selected by the user but we may not be able to show all the available fields for the given {{issueTypes}} due to slack restrictions. In that case , we show the user a warning message and ask them to create the issue from jira if they still need to fill in those fields. h3. Suggested Solution Would be useful if there was a way to set the form from the {{/jira create}} per project per channel h3. Why this is important That way, the issue created in Jira, through Slack, would be completed filled, not needing to enter the issue after its creation to provide more information not available in the creation from on Slack |
| Link |
New:
This issue is duplicated by |
| Remote Link | New: This issue links to "Page (Confluence)" [ 529848 ] |
| Description |
Original:
h3. Problem Definition
At this moment, the {{/jira create}} command doesn't have the option to customize which fields will be filled during the creation of the issue. h3. Suggested Solution Would be useful if there was a way to set the form from the {{/jira create}} per project per channel h3. Why this is important That way, the issue created in Jira, trough Slack, would be completed filled, not needing to enter the issue after its creation to provide more information not available in the creation from on Slack |
New:
h3. Problem Definition
At this moment, the {{/jira create}} command doesn't have the option to customize which fields will be filled during the creation of the issue. h3. Suggested Solution Would be useful if there was a way to set the form from the {{/jira create}} per project per channel h3. Why this is important That way, the issue created in Jira, through Slack, would be completed filled, not needing to enter the issue after its creation to provide more information not available in the creation from on Slack |