Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,507
Community Members
 
Community Events
184
Community Groups

Using portfolio sprint start date for Target Start date in Automation Rules

Edited

My goal is to be able to send automated emails to clients reminding them of inputs that are due prior to the beginning of the sprint that their work is assigned to. 

The inferred sprint date the portfolio tool (see screenshot) shows in the "target start" field does not show up as an actual "target start" date in jira, even after being committed in the plan.  Additionally the inferred sprint date on the plan is not searchable with JQL using "target start" as a search parameter, nor can I query the issues in a sprint in a specific date range using the futuresprint() function, leaving me without a way to trigger automation rules without manually adding the inferred sprint date.

I understand that these two data points are different.  but what I am looking to do is bridge the gap (automatically) so that I dont have to manually enter the target dates when a task is associated with a sprint.Screenshot 1.png

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events