NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

National Cancer Institute Center for Biomedical Informatics and Information Technology
caDSR Sprint 1.TBD 50.3.0 Release Notes

To remove a ticket from Jira macro output on this wiki page, add the NRN label to the ticket.

To add a ticket, consider why the ticket doesn’t already match the appropriate query:

  • Does it have the NRN label or the appropriate KnownIssueSprint label?
  • Is it in one of the current sprints?
  • What’s the Issue Type, Status, and Resolution?

Wiki troubleshooting tips:

  • Log out of the wiki and log back in.
  • Try a different browser. 
  • Clear browser cache, close all browser tabs and windows, and log in again. 
  • Contact NCI help desk
    Excerpt

    TBD

    Hidden Data

    16-Nov-2023

    Improvements

    The following are tracker numbers and descriptions of improvements.

    Advanced Tables - Table Plus
    sortColumn1
    Table Transformer
    dateFormatdd M yy
    export-wordfalse
    export-csvfalse
    separator.
    version2
    export-printfalse
    sqlSELECT 'Epic Link' as 'Feature', 'Summary' as 'Description', 'Key' as 'Jira Tracker Number' FROM T*
    transposeResultfalse
    show-sourcefalse
    plainTextfalse
    id1695924784843_-597278440
    transposefalse
    worklog365|5|8|y w d h m|y w d h m
    export-pdffalse

    Jira
    serverNCI Tracker
    columnIdscustomfield_12350,summary,issuekey
    columnsEpic Link,summary,key
    maximumIssues1000
    jqlQueryfilter=TBD
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    Hidden Data

    In the above Jira macro, replace TBD with the filter number for the Improvements list in the current sprint.

    Copy sprint numbers from Rui's "MWS Sprint" filter into the new Jira filter criteria and below:

    • Sprint in (TBD) 
    • AND (labels not in (NRN) OR labels is EMPTY)
    • AND resolution = Fixed
    • AND issuetype != Bug
    • ORDER BY summary ASC

    When the team deploys this Sprint to Stage:

    1. Add an Epic Link to each ticket above that doesn't already have one. 
    2. In each ticket Summary, delete the prefix if it duplicates the Epic Link.
    3. In each ticket Summary, add ending punctuation and otherwise copyedit, if necessary.

    When the team deploys this Sprint to Production:

    1. Open this page in view mode and copy the output of the Jira macro.
    2. Open this page in edit mode and paste the table. 


    Bug Fixes

    The following are tracker numbers and descriptions of bug fixes.

    Advanced Tables - Table Plus
    sortColumn1
    Table Transformer
    dateFormatdd M yy
    export-wordfalse
    export-csvfalse
    separator.
    version2
    export-printfalse
    sqlSELECT 'Epic Link' as 'Feature', 'Summary' as 'Description', 'Key' as 'Jira Tracker Number' FROM T*
    transposeResultfalse
    show-sourcefalse
    plainTextfalse
    id1695924940765_171141476
    transposefalse
    worklog365|5|8|y w d h m|y w d h m
    export-pdffalse

    Jira
    serverNCI Tracker
    columnIdscustomfield_12350,summary,issuekey
    columnsEpic Link,summary,key
    maximumIssues1000
    jqlQueryfilter=TBD
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    Hidden Data

    In the above Jira macro, replace TBD with the filter number for the Bug Fixes list in the current sprint.

    Copy sprint numbers from Rui's "MWS Sprint" filter into the new Jira filter criteria and below:

    • Sprint in (TBD) 
    • AND (labels not in (NRN) OR labels is EMPTY)
    • AND resolution = Fixed
    • AND issuetype = Bug
    • ORDER BY summary ASC

    When the team deploys this Sprint to Stage:

    1. Add an Epic Link to each ticket above that doesn't already have one. 
    2. In each ticket Summary, delete the prefix if it duplicates the Epic Link.
    3. In each ticket Summary, add ending punctuation and otherwise copyedit, if necessary.

    When the team deploys this Sprint to Production:

  • Open this page in view mode and copy the output of the Jira macro.
  • Open this page in edit mode and paste the table. 


    Issues Not Fixed in This Sprint

    The following are tracker numbers and descriptions of unresolved issues.

    Advanced Tables - Table Plus
    sortColumn1
    table-joiner
    Feature
    dateFormat
    Description
    dd M yy
    export-wordfalse
    export-csvfalse
    join-columnEpic Link
    separator.
    version2
    export-printfalse
    sqlSELECT 'Epic Link' as 'Feature', 'Summary' as 'Description', 'Attachment Description' as 'Workaround', 'Key' as 'Jira Tracker Number' FROM T*
    transposeResultfalse
    show-sourcefalse
    plainTextfalse
    id1692026983273_-1612685466
    transposefalse
    worklog365|5|8|y w d h m|y w d h m
    export-pdffalse

    Jira
    serverNCI Tracker
    columnIdscustomfield_12350,summary,customfield_10758,issuekey
    columnsEpic Link,summary,Attachment Description,key
    maximumIssues1000
    jqlQueryfilter=TBD
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    Hidden Data

    In the above Jira macro, replace TBD with the filter number for the Not Fixed list in the current sprint.

    Copy sprint numbers from Rui's "MWS Sprint" filter into the new Jira filter criteria and below:

    • Sprint in (TBD) 
    • AND (labels not in (NRN) OR labels is EMPTY)
    • AND resolution = "Won't Fix" 
    • ORDER BY summary ASC

    When the team deploys this Sprint to Stage:

    1. Add an Epic Link to each ticket above that doesn't already have one. 
    2. In each ticket Summary, delete the prefix if it duplicates the Epic Link.
    3. In each ticket Summary, add ending punctuation and otherwise copyedit, if necessary.
    4. For each bug, copy the workaround from the Workaround field into the Attachment Description field, so this macro will display it in the Workaround column.
    5. For each non-bug, add "No workaround" to the Attachment Description field.

    When the team deploys this Sprint to Production:

    1. Open this page in view mode and copy the output of the Jira macro.
    2. Open this page in edit mode and paste the table. 

    Known Issues Found in Sprint 1.TBD Testing - Planned for Next Sprint

    The team created or reopened the following issues during Sprint 1.TBD testing.

    Advanced Tables - Table Plus
    sortColumn1
    Table Transformer
    dateFormatdd M yy
    export-wordfalse
    export-csvfalse
    join-columnEpic Link
    separator.
    version2
    export-printfalse
    sqlSELECT 'Epic Link' as 'Feature', 'Summary' as 'Description', 'Key' as 'Jira Tracker Number' FROM T*
    transposeResultfalse
    show-sourcefalse
    plainTextfalse
    id1695925018561_298248446
    transposefalse
    worklog365|5|8|y w d h m|y w d h m
    export-pdffalse

    Jira
    serverNCI Tracker
    columnIdscustomfield_12350,summary,customfield_10524,issuekey
    columnsEpic Link,summary,Workaround,key
    maximumIssues1000
    jqlQueryfilter=TBD
    serverId7954a81f-12da-3366-a0ef-97c806660e7c

    Hidden Data

    In the above Jira macro, replace TBD with the filter number for the Known Issues list in the current sprint.

    Update the label in the filter and below:

    • project = DSRMWS
    • AND resolution = Unresolved
    • AND labels = KnownIssueSprintTBD
    • ORDER BY summary ASC

    When the team deploys this Sprint to Stage:

    1. Add the KnownIssueSprintTBD label to tickets in DSRMWS-TBD that don't have strikethrough in the ticket description. (Those tickets haven't been resolved yet.)
    2. If one of those tickets is resolved before the release, remove the label from that ticket, so this macro won't display it.
    3. Add an Epic Link to each ticket above that doesn't already have one. 
    4. In each ticket Summary, delete the prefix if it duplicates the Epic Link.
    5. In each ticket Summary, add ending punctuation and otherwise copyedit, if necessary.

    When the team deploys this Sprint to Production:

    1. Open this page in view mode and copy the output of the Jira macro.
    2. Open this page in edit mode and paste the table. 

    Release History

    ...



    Known Issues Found in Sprint 1.50.3.0 Testing - Planned for Next Sprint

    The team created or reopened the following issues during Sprint 1.50.3.0 testing.

    Advanced Tables - Table Plus
    sortColumn1



    Release History

    ReleaseDate
    Sprint 1.50.3.016-Nov-2023
    Sprint 1.49.1.024-Oct-2023
    Sprint 1.48.4.025-Sep-2023
    Sprint 1.47.3.030-Aug-2023
    Sprint 1.46.4.0: Emergency Patch2-Aug-2023
    Sprint 1.46.3.027-Jul-2023
    Sprint 1.45.2.029-Jun-2023
    Sprint 1.44.3.01-Jun-2023
    Sprint 1.43.5.04-May-2023
    Sprint 1.42.5.04-Apr-2023
    Sprint 1.42.4.030-Mar-2023
    Sprint 1.41.5.016-Mar-2023
    Sprint 1.41.4.014-Mar-2023
    Sprint 1.41.3.016-Feb-2023
    Sprint 1.40.2.012-Jan-2023
    Sprint 1.39.2.05-Dec-2022
    Sprint 1.38.2.010-Nov-22
    Sprint 1.38.1.07-Nov-22
    Sprint 1.37.2.020-Oct-22
    Sprint 1.37.1.0(Not deployed.)
    Sprint 1.37.0.0(Not deployed.)
    Sprint 1.36.4.04-Oct-22
    Sprint 1.36.3.026-Sep-22
    Sprint 1.35.3.07-Sep-22
    Sprint 1.35.2.0(Not deployed.)
    Sprint 1.35.1.025-Aug-22
    Sprint 1.34.1.1    9-Aug-22
    Sprint 1.34.0.028-Jul-22
    Sprint 1.33.1.07-Jul-22
    Sprint 1.33.0.0(Not deployed.)
    Sprint 1.32.2.022-Jun-22
    Sprint 1.32.1.016-Jun-22
    Sprint 1.32.0.019-May-22
    Sprint 1.31.0.011-May-22
    Sprint 1.30.0.025-Apr-22
    Sprint 1.29.0.0(Not deployed.)
    Sprint 1.28.0.015-Apr-22
    Sprint 1.27.0.029-Mar-22
    Sprint 1.26.0.09-Mar-22
    Sprint 1.25.0.017-Feb-22
    Sprint 1.24.0.03-Feb-22
    Sprint 1.23.0.011-Jan-22
    Sprint 1.22.0.014-Dec-21
    Sprint 1.21.0.015-Nov-21
    Sprint 1.20.0.01-Nov-21

    ...


    Include Page
    CSS Stylesheet 1
    CSS Stylesheet 1

    ...