Sprints in Jira Work Management

[Kyle Yan]

Since the release of automation limits set to Jira Software Projects, I thought it would be a good idea to move Jira Software Projects to a Jira Work Management project type to decrease the number of automations.

I am now stuck with those that still use the Jira Sprint functionality.

Has anyone found a workaround for Sprints in the Jira Work Management?

[John Funk]

Hi Kyle,

I would use a combination of the two project types. Leave your Sprint work in Jira Software and move your business related projects to Jira Work Management. 

One way to reduce the number of executions to a rule is to make the rule a schedule rule running once a day (or more during business hours if need be) instead of every time an action happens - like creating an issue or updating a field. If the results of the rule firing are not really time critical, then run them one or a few times a day. 

[Trudy Claspill]

Hello @Kyle Yan 

The automation limits apply to Jira Work Management projects also. Refer to

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

The limit on rule execution is actually higher for Jira Software (1700) than for Jira Work Management project (1000).

And you get each of those limits. You get 1700 executions for rules scoped strictly to Software projects, and 1000 executions for rule scoped strictly to JWM projects. Rules that are scoped to multiple types of projects will be counted against the Product with the higher limit (Software).

On what exactly are you basing your decision to transition from Software projects to Work Management projects?