Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.

Mapping Sprints

Idea ID 2835436

Mapping Sprints

Hi

Referencing to the idea from @Nataliia Positko :

https://community.microfocus.com/t5/ALM-Octane-Idea-Exchange/Support-of-multiple-sprints-in-Octane/idi-p/2835199

would like to suggest the temporary solution for MFConnect until Octane supports multiple Sprints for Defect (and maybe other entity types):

In Data Sources with Product Type = Jira , it would be nice to have an option to specify the rule for MFConnect to pick the single Sprint out of multiple.

Possible options could be:

Use the Sprint with greatest/lowest ID

Use the Sprint with alphabetically greatest/lowest Name

Use the Sprint with greatest/lowest Start Date

Use the Sprint with greatest/lowest End Date

etc

5 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: New Idea

Good idea.

I'm wondering if there's sense in additional conditions based on the date/time at which the sync is running.
For example:
"Use the Sprint with lowest End Date that is in the future from the current date at sync"

Are there any others like this that come to mind?

 

Micro Focus Expert
Micro Focus Expert

According to R&D  there are existing calculated value MIN & MAX functions which will not require new conditional operators.

Here is the link to the documentation

https://admhelp.microfocus.com/connect/en/4.0-4.3/Online/Content/Topics/calculated-values.htm?cshid=calculated

the functions are…

Max(type, property)

The largest of a set.

Min(type, property)

The smallest of a set.

 

So for example, you should be able to use Max(Sprint, EndDate) and it should produce the desired sprint.

Or to assign stories to the current sprint (for example) or assign a sprint to the appropriate release by date (assign sprint to release where sprint end date <= release end date AND sprint start date >= release start date)

Micro Focus Expert
Micro Focus Expert
Status changed to: Needs Clarification

Hi Vitaliy.

 

I understand that the description of this idea does NOT actually match your needs (additional need for filtering on subsets of sprints)?

Would your please clarify and/or refine your idea description?

 

Best Regards,

Dom.

Commander
Commander

Hi @Dominique Kaiser 

You are right, using calculated values with functions for Master (Octane) side in Defects type mapping is not correct in our case. Because it will lead to the situation when all the Defects in the synch. scope will get the same (with max/min Start/End Date among all in the project) "Sprint" field value on the Master (Octane) side, regardless the "Sprint" field value(s) on Target (Jira) side that mapped issue has.  

What we actually need is to map Jira's Sprint field with Octane's Sprint field for Defects.

The problem is that in Jira this field is cummulative. It gathers all Spints that Defect has been associated with during its lifecycle. So this field is multi-value. In Octane the Sprint is single-value field. 

My idea was to add an option in Jira-type Data Sources which describes the way of "conversion" multi-value Sprint field to single value, providing several possible options for conversion (please check the topicstarter message).

So that it is possible to add Sprint (Jira) to Sprint (Octane) field mapping for Defects in the MFConnect links and it will not fail when meet multiple values in Sprint field on Jira side.

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

We'll likely not add a dedicated capability for special scenarios like this - it is too involved and too hard to make work in generic situations instead of just one single scenario (single scenario is not acceptable for something like this)

However, we are considering adding a generic scripting capability in the medium-term that would allow you to run a custom script during synchronization.

As such, I'll not decline this idea - but I'll also not advance it any further than "Waiting for Votes", for now.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.