Setting up an internal request for new product features

[tom.sheffield]

This may be a silly question but, I am looking for a simple way to set up a way for folks internal to our company to submit ideas for new features and functions to existing and new products on the drawing board using a form.  Want to be able to have them fill out a form that will then be vetted and determined whether or not it makes sense, if there is additional information needed, and be able to "close the loop" on the submission more or less like it would be handled if submitted by an external customer.  

Any suggestions?

Thank you in advance.

Tom.

[Mark Higgins · Accepted solution]

Hi Tom,

You'd like people to fill out a form, and then you'd like the idea to be vetted (approved / rejected). 

The 'form' can be built by going to Project Settings, select Forms and then build your self a form.

There are templates you could use, or build your form, by adding fields.

The second part, suggests you'd like an approval process, which could be the Service Request - with Approvals.

Hope that helps, all you'd like a bit more.

Cheers

mark

[tom.sheffield]

Hi Mark,

Thank you for the guidance and that was right on the mark.  The next thing I am needing to work through is a method for once the submissions are vetted, I need to figure out how to route them to the appropriate projects within Jira.  I am confident someone has already "cracked this nut" but it sure would be nice to get pointed in the right direction.

TOm.

[Mark Higgins]

Hi Tom,

When you say 'route them to the appropriate project', do you mean you want to create a ticket in project A, or project B, etc, depending on something on the 'form'?

Suggest you will need an automation rule, that will clone the ticket to the project that you want.

So, if field A = laptop then clone ticket into the laptop project, else if field A = mouse then clone ticket into the mouse project.

Have a look at this:

https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/

Cheers

Mark

[tom.sheffield]

Hi Mark,

I really appreciate you help.

It think so.  Just to make sure I got it right....

Tickets are created from form and placed in a project say "new feature request".  These are then reviewed and determined if they meet certain criteria and have all of the details need to be considered ready to be routed to the appropriate development team's project for grooming purposes.  There may be additional administration activities required before this transition can occur so I don't want it to be cloned until it is ready.  So, based on this, I think we can accomplish what I am envisioning by not setting the field value for where we want it cloned into until that value is added.  Did I get that right?

[Mark Higgins]

Hi Tom,

Yes, you just need to tailor the automation rule, so that it does not fire, until all the fields that you want to be set up, are set up.

Let me know how you go.

Cheers

Mark