Use current sprint in jira Automation rules

[snwatts6]

Hi, I would like to write an automation rule that looks at the current sprint for cards that are in a done status and fix version is empty.  I am not sure how to identify the current sprint in the rule automatically.  I dont want to use the current sprint number or name as I want the automation rule to work each sprint with out making any changes. Has anyone done this before and can show me a coding example?  

[David Ray]

Please give us a way to set the default issue type in the next-gen project.

Right now ours is Story, which is not often intentionally used, and we'd like it to be Task.

[william]

Do you know if there is a solution to this in next-gen project?

[AhmadDanial]

Hi, Jade.

By default, JIRA Administrators have the ability to change the default issue type displayed on the Create Issue screen with reference to the How to change the default issue type displayed at the Create Issue screen. KB.

Once a user has created an issue in a project in the current session, JIRA retains the issue type from the previous issue any time the user creates a new issue in the same project. This is intended to make it easier for users to quickly create issues, such as when a software developer is creating a number of stories for a sprint or a QA engineer is filing bugs.

Since the behavior that you are experiencing on your end differs from your colleague, I would like to understand if it stems from the environment itself.

• Can you please let me know if you tested this on the same web browser on the similar version?
• Have you tested this on Google Chrome's Incognito / Safari's Private mode so we can confirm that it is not a cache issue?
• Any other users experiencing the same issue (defaulted back to Design Story)?

Looking forward to hear from you soon.

[Stephen Wille]

The instructions on the link for changing the default issue type doesn't seem to map to the new Jira.  So far I have not been able to find a way to do this.

[Deleted user]

Yes -- this doesn't seem to work with what I am seeing either.

[Ismail]

Hmm...its  Apr 2020 still this is the same...its not available in the next-gen project. Everytime we need to change Story to Issue and we keep on forget to choose....

[Josh Empson]

We would also very much like this functionality, to force users to select the appropriate issue type as opposed to just the same one they used last time - this will save us an awful lot of time gathering this data after the ticket has been created.

[william]

This guide does not work for me either :(

[william]

I have found a fix for this :)

Go to Project settings > Apps > Project automation > Create rule. 

You can set an automation rule to always select tasks when creating a ticket.

Hope this helps

[Santosh Subramani]

Hello @william 

can you share the screenshot of your automation rule

[william]

@Santosh Subramani  hope this helps, I also created one that forces the ticket to be assigned to the user that created it if they forget to select anything. 

[william]

[Santosh Subramani]

Hello @william , '

Thanks for the reply. 

Following automation , its create a task issue type even if you choose to create epic. 

that's is not the intended behavior 

What user wants is when the click on create button , For all the user it should load as task type by default , if they wish they can change the issue type too.