Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Ignoring Relationships using CALCULATE

Data model is following:
1. Table JIRA_ISSUE - contains all JIRA items;

2. Table JIRA_SPRINT_CALENDAR - contains Sprint data (Start and Release dates)
3. Between these 2 tables, there is created Relationship (Many to One) JIRA_ISSUE[Sprint VersionID] <-> JIRA_SPRINT_CALENDAR[VersionID]

I need to get count of JIRA issues per Sprint Month. For example, if during the Feb-2019 there was 2 Sprints, I need to COUNT all items per month. Currently, problem is, that used measure is counting Jira issues per month & sprint (I suspect that it is due to existing RELATIONSHIP).
Please help with this measure:

EVALUATE
CALCULATE (
    COUNTROWS ( JIRA_ISSUE ),
    ALL ( JIRA_ISSUE ),
    JIRA_ISSUE[Issue Type] = "Story",
    JIRA_ISSUE[Status] <> "Story: Not Required",
    NOT ISBLANK ( JIRA_ISSUE[Sprint VersionID] ),
    FILTER (
        ALL ( JIRA_SPRINT_CALENDAR ),
        YEAR ( JIRA_SPRINT_CALENDAR[Release Date] )
            = YEAR ( MAX ( JIRA_SPRINT_CALENDAR[Release Date] ) )
            && MONTH ( JIRA_SPRINT_CALENDAR[Release Date] )
                = MONTH ( MAX ( JIRA_SPRINT_CALENDAR[Release Date] ) )
    )
)
  • Anonymous's avatar
    Anonymous
    7 years ago

    Issue was resolved by changing Data Model.

2 Replies

  • v-yulgu-msft's avatar
    v-yulgu-msft
    Microsoft Employee

    Hi Anonymous ,

     

    Please try this measure:

    EVALUATE
    CALCULATE (
        COUNTROWS ( JIRA_ISSUE ),
        ALL ( JIRA_ISSUE ),
        JIRA_ISSUE[Issue Type] = "Story",
        JIRA_ISSUE[Status] <> "Story: Not Required",
        NOT ISBLANK ( JIRA_ISSUE[Sprint VersionID] ),
        ALLEXCEPT (
            JIRA_SPRINT_CALENDAR,
            YEAR ( JIRA_SPRINT_CALENDAR[Release Date] ),
            MONTH ( JIRA_SPRINT_CALENDAR[Release Date] )
        )
    )

    For more advice, please post sample data of JIRA_ISSUE and JIRA_SPRINT_CALENDAR, and show us your expected result. How to Get Your Question Answered Quickly

     

    Best regards,

    Yuliana Gu

    • Anonymous's avatar
      Anonymous
      Not applicable

      Issue was resolved by changing Data Model.