Forums

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

When requiring Parent field when making a story, will other apps like Miro respect the requirement?

Walker Heflin June 27, 2024

I am seeing many links about how to make the parent field required when making a story. BUT will other apps like Miro/Slack/Excel/Outlook, etc. detect filling in the parent field is required and make that required in their app too?

If so what needs to be set up in either Jira or the respective apps?

I am concerned if the app does not require this field upfront then the story will go into the ether and be lost. 

Help appreciated

1 answer

1 vote
Dave Rosenlund _Trundl_
Community Champion
June 27, 2024

Hi, @Walker Heflin 👋

Unfortunately, the answer is 'probably not.'  Or, 'it will depend.' Meaning it will depend on how each app was developed and by whom (and whether or not the developer saw it as a requirement).

Honestly, I'm even sure there is an API that covers this use case — but maybe someone else will know.

Best,

-dave

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 27, 2024

Hi @Walker Heflin 

Yes, and...to Dave's answer:

It is possible to call the REST API and get the required fields for an issue create: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-createmeta-projectidorkey-issuetypes-issuetypeid-get

and

https://www.atlassian.com/blog/developer/creating-a-jira-cloud-issue-in-a-single-rest-call

 

As Dave describes, the question is will a vendor do that before calling the create issue endpoint...or not?  If they do, perhaps they could dynamically detect and ask for the required fields.  If not, I would expect the create issue call will fail and the vendor app will need to handle / surface that information.

Even in Jira Cloud's own automation rules, the actions for issue create and clone are generic: they do not detect the required fields (beyond Project, Issue type, and Summary) and instead the rule action fails when it runs.  IMHO, this makes sense to reduce the complexity of the rule editor, and because the fields' required nature could change over time (breaking the rule due to outside changes).

Kind regards,
Bill

Like Dave Rosenlund _Trundl_ likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events