Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

How to pull correct project start and end dates into filters?

Edited

We use filters for a subset of users to see cards with specific labels. 

Screenshot 2023-10-30 at 2.14.53 PM.png

In the filtered view, we have project start and project end date pulled in from the JPD project. The dates do not match what is configured on the JPD card. 

 

For example, we have a projected start date of 7/31/23 and projected end date of 11/30/2023. 

Screenshot 2023-10-30 at 2.37.16 PM.png

On the filtered view, project end date lists the following: 

 

{"start":"2023-11-30","end":"2023-11-30"}

Screenshot 2023-10-30 at 2.16.04 PM.png

Additionally, we have a due date filter for non-JPD cards and the due date listed is 10/27/23. The linked delivery card also are due with work estimates of 11/30/23.

 

Wondering where these dates are coming from? Potential bug?

2 answers

Suggest an answer

Log in or Sign up to answer
0 votes
Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 31, 2023

Hi Chelsea, 

Could you please elaborate on the reason why you are using the filtering in JQL and not create a dedicated view for these contributors? 

Jira Product Discovery dates fields are a bit different than non-JPD date fields. 

One field value is always composed of a start and end date (because you could select a quarter instead of a specific day), e.g. if you'd select this quarter, it would look like 

Screenshot 2023-10-31 at 13.21.19.png

{"start":"2023-10-01","end":"2023-12-31"} 

So in your screenshots and examples - I see that on your first screenshot, you only display the field "project target date" but not the field "project start".

 But I can guess that when you will display the field project start you will see {"start":"2023-07-31","end":"2023-07-31"} 

All this to say - our date field is definitely not to be used with the Jira filtering because the Jira platform doesn't know how to interpret it. :/ 

Hi Hermance - 

 

In terms of the following question, do you mean a dedicated view within the JPD project? 

 

Could you please elaborate on the reason why you are using the filtering in JQL and not create a dedicated view for these contributors? 

 

Thanks!

Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 02, 2023

Hey @Chelsea Duke Miller yes exactly

@Hermance NDounga -

 

We are using filters so we can pull in cards from different projects, outside of the JPD project. Are you suggesting we should pull different projects into one view? 

Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 03, 2023

@Chelsea Duke Miller thanks for exaplaining your use case, I was simply curious to understand the reason why you need to get "off" JPD to achieve what you want. but as it's not possible to display cards from various projects in one Jira Product Discovery view, I do understand now :) 

Thank you for sharing! Will definitely use if I export. 

TAGS
AUG Leaders

Atlassian Community Events