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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

Eazybi, Only issues where Team was X in particular month Edited

Hi

 

Backstory:

Because of the current way a created vs resolved per month bar is set up, if someone edits an issue in Jira to match the criteria (a custom field called 'Team'), it gets sucked into the report/dashboard, this can damage their stats as it looks like they missed a ticket that month.

 

What I'd like is for the created vs resolved report to only include month on month issues where the team field was set to X no later than the last day of that month.

 

So for the July report if we check on August 1st at 7am that there were 1000 created and 1000 resolved by the Desktop team in July, if at 10am someone changes an issue to Desktop team, that it wont show for July 1001 created and 1000 resolved, because it wasn't technically allocated to the Desktop team until August 1st.

 

I hope this makes sense.

 

I'm also in the process of switching these reports away from using a custom field to using assignee group

 

Thanks

1 comment

Hi @Steve Letch


You can try to create a calculated member in the Measures dimension, which will count all the issues meeting the criteria. However, the field "Team" has to be a single value field cause eazyBI can import value changes only for that type of fields.

First, add the parameters to the eazyBI advanced settings for the custom field, enabling the value change option - https://docs.eazybi.com/eazybijira/data-import/custom-fields/advanced-settings-for-custom-fields.

Please have a look at the code below:

[jira.customfield_NNNNN]
data_type = "string"
dimension = true
separate_table = true
changes = true

Replace NNNNN with the ID of the custom field. After updating the eazyBI advanced settings, you can select the "Import value changes" option for this custom field in the eazyBI import settings.

Also, please enable the "Issue change history" option if it is disabled - https://docs.eazybi.com/eazybijira/data-import/jira-issues-import/import-issue-change-history.


Then you can create the calculated member in the Measures dimension calculating the number of issues matching the criteria. Please have a look at the code below:

NonZero(Count(
Filter(
Descendants([Issue].CurrentHierarchyMember,[Issue].[Issue]),
--created in period no last minute changes
(DateInPeriod(
[Measures].[Issue created date],
[Time].CurrentHierarchyMember
) AND
--change custom field more than 10 hours before period end
DateDiffHours(
([Measures].[Transition to status first date],
[Transition Field].[Team]),
[Time].CurrentHierarchyMember.NextStartDate
)>= 10)
OR
--created in previous period with some last minute changes
(DateInPeriod(
[Measures].[Issue created date],
[Time].CurrentHierarchyMember.PrevMember
) AND
--change custom field in last 10 hours
DateDiffHours(
([Measures].[Transition to status first date],
[Transition Field].[Team]),
[Time].CurrentHierarchyMember.NextStartDate
) < 10)
)
))

The calculation relays that you have the Time dimension "Month" level members in the report.


Kind regards,

Roberts // eazyBI support

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you