Make field required - does not work consistently

Anette Noll May 11, 2023

Hi all,

sure anyone can help me with this; following scenario:

  1. Field configuration scheme for issue type A
  2. here I make field description required
  3. I create an issue of issue type A
  4. field description is required; all is fine

 

In the following case it does not work:

  1. I create issue of issue type A from inside workflow of issue type B
  2. field description is not required anymore in create screen of issue type A

Jira 1.PNG



2 answers

0 votes
Karim ABO HASHISH
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2023

hi @Anette Noll 

Could you please elaborate more on the solution you've implemented to create an issue from B into A. Does B and A use the same workflow.

Awaiting your return

Cheers,

Karim

Anette Noll May 14, 2023

Hi Karim ABO HASHISH,

B and A do use different workflows. Workflow B contains Create Issue(s) postfunction. This normally works. 

I have the impression that original Jira fields like description and comment, work  somewhat differently in comparison to custom fields.

Therefore in the meantime I created a custom field that works as it is intended.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2023

Jira doesn't do "create issue" as part of a workflow. 

You can create automations, listeners, and post functions to do it, but I'm not sure what you have done here, so I'm a bit stuck on what you have set up.

Suggest an answer

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

Atlassian Community Events