This article describes how to do what I need, but additional field types are needed: date or date/time, and the priority field: https://support.atlassian.com/jira/kb/how-to-link-a-custom-field-with-the-prompt-action-input-with-manual-triggers-in-jira-automation/
The current functionality won't solve for the use case:
When a manual automation trigger is used to create a duplicate request and link it with the current request, the Reporter must enter values in a date field, a time field (or a date/time field) and the Priority field before submitting, but those field types (date and time (or date/time) and Priority fields) are not available.
These 5 field types are currently the only ones available:
* Short Text
* Paragraph
* Dropdown (Single Select)
* Number
* Checkbox
I'd prefer to not have to create a crazy work-around to provide the requested functionality. Of course I'd love to see Atlassian extend the existing functionality to include all custom field types (or at least Date, Time, Date/Time, and Priority fields), but in the meantime, are there any suggestions for how this might be achieved without making the system brittle and overly complex?
Hi @Trevan Householder_Isos-Tech-Consulting_
What you describe for expanding options for user inputs is part of several open suggestions, including at least these:
https://jira.atlassian.com/browse/AUTO-744
https://jira.atlassian.com/browse/AUTO-1729
Regarding workarounds with the present features, you could:
Kind regards,
Bill
Thanks Bill, I'll give it a go...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.