Material Move Request Project

[Preston_Warden]

Hello.

I am completely new to Jira and am trying to demonstrate the benefits of using JIRA compared to other softwares for ticketing.

I am attempting to create a few of the following:

I want to create a "move request". Therefore, a user submits a request that a chair be moved. The request goes to facilities, facilities can either assign it to a user, mark as pending, or mark as cancelled or on hold.

Once facilities completes the move, they can mark as complete.

I would want two pending types: pending move, pending delivery.

When pending delivery, it would alert another employee that the "chair" is unavailable and one needs to be ordered. Which then submits it's own form ticket to order the material and make that a task.

I know this is a lot of info, but I am unsure of how to use JIRA yet.

[Earl_McCutcheon]

Hello Preston,

Thanks for the breakdown on what you're looking for, and welcome to Jira and the community forum.

What you are looking to accomplish can be done using Jira Service Desk Automation rules. Alternatively if your not using Jira Service Desk and only have Jira Software or Core there are add-on apps you could use like Automation for Jira, or  Add Issue on Transition for Jira Cloud, or  ScriptRunner for Jira, as an exe of some apps that would give you additional options for this in the alternate Jira options.

Next as a referance point the following Documentation page is a collection of the various options avaliable for this feature in Service Desk with links to sub pages for the specific actions:

• Set up rules to automate repetitive tasks

The approach would be that the end user creates a "move request" in your Service desk project, and on the various transitions set up an Automation rule so that if the transition is used a deferent automation rule will be triggered for the desired follow up actions.

EXE: For your two pending types, pending move and pending delivery,  with the requirement:

When pending delivery, it would alert another employee that the "chair" is unavailable and one needs to be ordered. Which then submits it's own form ticket to order the material and make that a task.

You can set up a Custom Rule where, when the status changes, it creates an issue in the alternate project, or in the same project but a different queues via request type to order the chair, with preset options selected, in turn linking the new issue to the original, it would look 'something like this:

On the alternate request set up one of the preset automation rules of "Update Jira linked issues" so that the desired message is added as a common depending on the status of the alternate request, so the user is updated when the chair is on order

Then set up another Automation Rule to Transition the issue through the approved or declined transitions based on the actions taken on the linked issue and it would look something like this:

But overall the automation rules are really powerful and you can get as complex as you would like to automate this action and set up various rules based on the exact needs.  You can also add in additional customization using workflow options such as post functions, validators, and conditions as covered in "Advanced workflow configuration" so that only certain options become avaliable for a user to select or set values to the issue when a transition occurs, and if that value is set it can be used to trigger a condition for one of your automation rules.

Regards,
Earl