nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using forms and moving a subtask

Dennis_H

Ok so this might be a bit complex. I'd like to create a form for a project that users can enter feature requests, and once a form is submitted an issue is created, however.....I'd like to find a way to move that issue and make it a subtask of a specific existing issue (not the parent or trigger issue)

I've created an issuetype called "Feature Request"

Set the form to use that issue type

New issue is created with issue type "Feature Request"

Now I'd like to automate moving that issue so it's a subtask of an existing issue (a regular task) called Feature Requests, so final goal is to have the feature request issuetype become a subtask of the Feature Request issue

Is this possible (without buying more add-ons)?

Accepted answers

Dennis_H

Well, it turns out you CAN set a specific issue in the Parent Issue setting, just click on the field (not the dropdown options) and start typing. Works perfectly. Would be nice if Atlassian mentioned that.

All comments

Ravi Sagar _Sparxsys_

Hi @Dennis_H

What are you trying to achieve by doing this? Are you trying to group those feature requests under a specific feature?

Why not use issue linking or better Epic links? Let us say those new issues come in your backlog and when you decide to deliver them or work on them or organise them then simple drag them to the Epic. If not Epic then may be use FixVersions along with Components.

Ravi

Dennis_H

This is for a classic business project so if I'm not mistaken we can't use Epics

Yes we want all user requests to go under a single issue as sub-tasks.

Dennis_H

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud