# Add "original cycle" field in jira for epics

XMLWordPrintable

## Details

• Type: Story
• Status: Won't Fix
• Resolution: Done
• Fix Version/s: None
• Component/s:
• Labels:
None
• Team:
SQuaRE

## Description

The last few days exposed that we need a new field in JIRA for epics, something like "original cycle". The problem is that if some epics are late (like the 29 W16 epics that are now assigned to X16 or F16): https://jira.lsstcorp.org/issues/?filter=14212

We had to manually track them down, just look at the filter:

 project = DM AND  issuetype = Epic AND  key in (DM-1109, DM-1111, DM-1117, DM-1123, DM-1233, DM-1955,   DM-1956, DM-1988, DM-2089, DM-2208, DM-2586, DM-3500,   DM-3559, DM-3578, DM-3581, DM-3594, DM-3602, DM-3622,   DM-3647, DM-3832, DM-3838, DM-3841, DM-3842, DM-3875,   DM-3876, DM-3878, DM-3887, DM-3906, DM-3909)  ORDER BY cf[10202] DESC, cf[10502] DESC, Cycle, WBS, Key 

So, as much as I hate to ask for another field, it will really help.

And we can always do a swipe through all epics when we are starting a new cycle and set these if they are not set, so hopefully it won't be much burden on anyone.

I don't feel strongly about the name, if someone has better suggestion than my "original cycle", let's call it something else!

## Activity

Hide
Jeff Kantor added a comment -

Kevin Long actually does track this in PMCS (or in Excel not sure which). It makes sense to have it in JIRA, but once we have the field, we should synchronize JIRA and PMCS information.

Show
Jeff Kantor added a comment - Kevin Long actually does track this in PMCS (or in Excel not sure which). It makes sense to have it in JIRA, but once we have the field, we should synchronize JIRA and PMCS information.
Hide
Jacek Becla added a comment -

Yes, he does but it was a very cumbersome process, he imported from jira to PMCS, then he produced a spreadsheet, I extracted the list of jira keys from his spreadsheet and built a filter, and then he asked me to send him the filter that I stitched together. I agree we should sync between JIRA and PMCS. (btw, how is it called in PMCS? It'd make sense to adopt the same name)

Show
Jacek Becla added a comment - Yes, he does but it was a very cumbersome process, he imported from jira to PMCS, then he produced a spreadsheet, I extracted the list of jira keys from his spreadsheet and built a filter, and then he asked me to send him the filter that I stitched together. I agree we should sync between JIRA and PMCS. (btw, how is it called in PMCS? It'd make sense to adopt the same name)
Hide
John Swinbank added a comment - - edited

Frustratingly, JIRA almost has this functionality built in with the WAS operator, but it only works on a few of the built in fields.

One of those built-in fields is "Fix Version", which I think we don't use in the DM project at the moment. Fix Version for an epic seems like it should be degenerate with Cycle. Can we just use it instead, and then get this functionality for free?

(I suspect the answer is that the disruption would be too great, but it does seem like the "right"/elegant solution).

Show
John Swinbank added a comment - - edited Frustratingly, JIRA almost has this functionality built in with the WAS operator , but it only works on a few of the built in fields. One of those built-in fields is "Fix Version", which I think we don't use in the DM project at the moment. Fix Version for an epic seems like it should be degenerate with Cycle. Can we just use it instead, and then get this functionality for free? (I suspect the answer is that the disruption would be too great, but it does seem like the "right"/elegant solution).
Hide
Jacek Becla added a comment -

I am in favor of doing it right, even if we have to bite a bullet and suffer for a bit

Show
Jacek Becla added a comment - I am in favor of doing it right, even if we have to bite a bullet and suffer for a bit
Hide
Frossie Economou added a comment -

John is correct in that if we used FixVersion, the answer would be trivial. Eg. to see the milestones we shifted:

project = DLP AND issuetype = Milestone and fixVersion changed ORDER BY fixVersion DESC

without the need of any extra field

Show
Frossie Economou added a comment - John is correct in that if we used FixVersion, the answer would be trivial. Eg. to see the milestones we shifted: project = DLP AND issuetype = Milestone and fixVersion changed ORDER BY fixVersion DESC without the need of any extra field
Hide
Tim Jenness added a comment - - edited

Did we decide against fixVersion?

Show
Tim Jenness added a comment - - edited Did we decide against fixVersion?
Hide
Xiuqin Wu [X] (Inactive) added a comment -

I don't think we made any decision on this.

Show
Xiuqin Wu [X] (Inactive) added a comment - I don't think we made any decision on this.
Hide
John Swinbank added a comment -

4 years later, I think we've been managing fine without this functionality.

Show
John Swinbank added a comment - 4 years later, I think we've been managing fine without this functionality.

## People

• Assignee:
Frossie Economou
Reporter:
Jacek Becla
Watchers:
Fritz Mueller, Frossie Economou, Jacek Becla, Jeff Kantor, John Swinbank, Kevin Long, Margaret Gelman, Simon Krughoff, Tim Jenness, Xiuqin Wu [X] (Inactive)