Issues with Form and Automation.

Kumari dvipa_pzaph8

Hi All,

Q1. Can I create Form for Epic issues type?

Q2 Can we apply any field where we can count "delay in days" of our task?

Actually, my company wants 'Delay in days' field is added automatically based on planned date. How we can do that? 

3. When I applied the automation for closing the issues [type 'Task'] from different issues [type "Order"]  (Both Issues type 'Standard Issue Type (Level 0)').  I am able to clone the issues from Task to order but problem is that I am not able to link cloned issues with task. I attached image. I want to see cloned issues with current issues from which these are cloned. Please help.

 

 

Thank you,

 

 

Ste Wright

Hi @Kumari dvipa 

Answers (and queries) below!

---

Q1: Can I create Form for Epic issues type?

When you say a Form, do you mean a...

• Custom Screen?
  • You can customise the screen for an Epic, instructions to help get you started can be found here...
    • Company-managed - https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/
    • Team-managed - https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/
• Form?
  • At present, Forms can only be at the stand issue type level. It is not possible to create them at Epic-level, or Sub-task
  • This is confirmed on this help page
  • There is a feature request for this, check out JWMCLOUD-329 

---

Q2: Can we apply any field where we can count "delay in days" of our task?

I assume the logic here is to populate a number field "Delay in Days" once per day, with the number of days past the "Planned Date"?

If yes, the rule will look something like this...

• Trigger: Scheduled
  • Run rule every = 1 Days
  • Run a JQL search... = TRUE (check box)
  • JQL - project = ABC and "Planned Date" is not EMPTY
  • Only include issues that have changed... = FALSE (uncheck box)
• Condition: {{smart values}} condition
  • First value = {{issue.customfield_10123}}
  • Condition = less than
  • Second value = {{now}}
• Action: Edit Issue
  • Field = Delay in Days
    • Value = {{issue.customfield_10123.diff(now).days}}

A few notes...

• The Custom Field ID used is the Planned Date's ID.

---

Q3: Link cloned Order to Task

You can set the Linked Issues value from Task (trigger), to Order (created issue action) from the fields' menu...

• Action: Create issue
  • Field = Linked issues
    • Value = clones, Trigger issue

---

Let us know if these help! If any details are inaccurate, or you have any additional questions, we'd be happy to assist.

Ste