Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Update all of these queries to reference your project (put "project = xyz AND " or "filter = 16632 AND " at the beginning of the JQL), then delete this info section. Best practice, review these queries and correct the data on at least a weekly basis. You can also save queries as favorites and subscribe.

If you are managing many Jira projects within a program and single collab page, such as an ESR project, creating a filter to reference all related work you need to monitor is most expedient and allows you to update a single filter if you need to add/remove a Jira project. For example, https://its-pro.ucsd.edu/issues/?filter=16632

*Created Recently Not By Me

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all issue types, except bugs, that have been created in your project within the past week. This is useful to ensure that any new issues are associated with the correct epic, in the correct project, etc., because that meta data is not visible in the emailed notification when they are created.

type != bug AND created >= -7d AND creator != currentUser() ORDER BY createdDate DESC, project ASC, "epic link" ASC, creator ASC

key summary created updated due assignee reporter priority status Epic Link project
Loading...
Refresh


EXC: Overdue

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all issues that are overdue and need an updated date.

resolution = unresolved AND duedate <= endOfDay() ORDER BY project, assignee, duedate ASC

key summary due assignee reporter status
Loading...
Refresh


EXC: Clean up estimates

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all issues estimated over 20 hours (excluding tasks associated with sessions), to be updated to ensure compliance with the SPM framework. 

type = task AND originalEstimate > 20 AND issueFunction in issuesInEpics("Object_type != Sessions ")

key summary created updated due assignee reporter status timeoriginalestimate timespent
Loading...
Refresh


EXC: Epic should be closed

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all epics where all tasks within are closed, so the epic should also be closed (or more tasks need to be added). 

issuetype = Epic AND status not in (Closed) AND issueFunction in epicsOf("issuetype in (Task,Story,Bug)") AND issueFunction not in epicsOf("status != Closed")

key summary due assignee reporter status
Loading...
Refresh


EXC: Open tasks on closed epics

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all tasks that are associated with closed epics, so the task should also be closed (or the epic reopened, or the task associated with an open epic). 

resolution = empty AND issueFunction in issuesInEpics(" status = closed ") ORDER BY "Epic Link"

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh


EXC: Open tasks associated with "Won't Do" or "Duplicate" epics

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all tasks that are associated with cancelled epics, so the task should also be cancelled (or the epic reopened, or the task associated with an open epic). 

resolution is EMPTY AND issueFunction in issuesInEpics(" (resolution = \"Won't Do\" or resolution = Duplicate) ") ORDER BY summary

key summary due assignee reporter status Epic Link
Loading...
Refresh


EXC: No Parent Link

Update all of these queries to reference your project or filter of projects, then delete this info section. 

This query shows all epics that are missing a parent link, which is necessary for them to render correctly in Jira plan.

"Parent Link" is EMPTY AND type = Epic ORDER BY project, duedate

key summary due assignee reporter status
Loading...
Refresh



  • No labels