How to trigger an issue on time?

[dD]

Hey folks I need your help.

I am new to the jira environment and stuggle with the automation ad-on.

My goal is to create an automated workflow, where on a specific days in a year a new issue is automatically created. This issue should then flow through my workflow.

1. Problem: The trigger: I use "Schedule" as my Trigger and created a cron expression with a specific date. However the rule doesnt work automatically but when I start the rule by manual it works fine and a new issue is created

2. Problem: My first status in the workflow is "open", because apparently the first status is the same over all workflows and I cant change the first status in one workflow without changing the first status in the other workflows (I dont understand this but I deal with it, so every workflow of mine starts with the "open" status. But this status is non relevant for my workflow and I want to automatically skip it. Hence I tried to extend the first rule with a new action and move the issue in the workflow to the next status. However this is also not possible and jira aks me to use the sql search. I just dont get it done.

[Heather Ronnebeck]

For item number 2. You need to go under the “issues” section of your administration tab and you can find it up in the top right hand corner of your screen. 

Then you need to go into workflows and create a new workflow. You can configure it however you’d like from there. Once you’re happy with it then you can apply it to your project and publish it. 

I highly recommend you always do this with any new project and never allow a workflow to share projects. This allows you the flexibility for each project in JIRA to be a snowflake. 

[Nic Brough -Adaptavist-]

I'd recommend that you share workflows as much as you possibly can.  This helps people work in similar ways across teams, keeps administration simple and enables you to report consistently across teams (in a lot of cases, where people have diverged on their workflows, cross-team reporting becomes impossible)

Imagine trying to run a bank's software development department and trying to get a simple report of "what stories are being worked on and by which team?" when you've got 3,000 workflows and 260 different status for "being worked on".

[dD]

Yes you are right, I will share the WF :) I just will change sth and then come back to you guys. I am amazed how fast you replay in this community :D

[Nic Brough -Adaptavist-]

1. Could you show us what you have configured for the schedule?

2. Edit the workflow, you can change the "create" transition so that it lands on another step.

[Jack Brickey]

One thing to remember is that the cron expression is going to be UTC time not your local time. So make sure you take them to consideration when testing

[dD]

@Jack You are right! this is the answer for the first problem :D Thaaank you :)