Setting up a process for internal requests

[Anders Hebert]

Hi all,

In our organisation we have multiple project (all set up as Company Managed projects).

I am looking for a simple way for employees to send in requests, ideas or business cases to different teams/projects. The team (or Jira-project members) would then go through these and decide if they will be worked on or not. 

I have looked into a few of ways of doing this (listed below), but would love to hear how others have solved this. 

1) Can I create a form which when submitted creates an issue in a Jira-project. If this could be in a Jira project menu. Is there such a standard functionality or marketplace add-on? Would the standard function "Issue Collector" work for this, or is that more designed for external website visitors?

2) Create a new issue type with custom fields. However, employees might not grasp how to use this or which project they need to create the issue in.

3) Create a Confluence page where employees type their request, idea or Business case into a template page - that the team goes through manually and creates the issue. Is there such a standard functionality or marketplace add-on?

4) Jira Work Management or Jira Service Management project set-up for only this purpose?

We are using Jira Software Cloud (Premium) and Confluence

[Jack Brickey]

what I might attempt here is to create a single project used to submit ideas. Then instruct the team to follow some standard simple input data in the description such as project = XXX. I would then set up an automation rule to scrub the description for the project information, and based on that the rule would create a new issue in the corresponding project and set the reporter to that user triggering the rule. Now you might simply leave off the automation and have all of your project owners review the incoming issues and decide if the idea is to move forward or not. If it does simply manually create an issue in their project.