Why I can't update jira "fix version" from QB? #1897

stevenlab · 1 decade ago

Why I can't update jira "fix version" from QB?

QB can released "versions" to jira and generated release notes, but it can't change field "fix version" for the filter I defined in jira. is it something wrong? thanks a lot!

replies 13
views 4938
stars 0

steveluo ADMIN · 1 decade ago

Hi,

Is there any error occurred in the build log? Or is there an Unprocessed report sub tab below the Jira issue tab found?

steveluo ADMIN · 1 decade ago

By the way, 'fix version' field will only be updated to issues with status Resolved or Closed. So, also check your issue status in JIRA.

stevenlab · 1 decade ago

it works after change the status to "fixed" <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing" />

but it only add a new value to "fix version" field, is there any way to replace existing value(or a option)? thanks a lot! <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" />

steveluo ADMIN · 1 decade ago

QuickBuild only adds new value instead of replacing the old one as an issue can be fixed in different versions, any special case you want to replace the value?

stevenlab · 1 decade ago

for example, I add a verion "Coming Version" and add some issues which we suppose to be displayed in releasenotes, and create filter for it.

after qb release it, I hope new version can replace "Coming Version" which we will use for next times.

we can see Coming Version in the road map from Jira, looks nice for the PM to plan/manage their sprints.

is it possible to add a option "overwrite existing field value" in the step? Thanks a lot! <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" />

steveluo ADMIN · 1 decade ago

No, currently, QuickBuild cannot overwrite the field.

I'm a little confused, why use 'Coming Version' instead of a specific version, for instance, 1.0.3.
In general, you will manage your issues in JIRA, and schedule some issues to your next version/release like 1.0.3, 1.0.4 for example, that is more suitable to show your roadmap. In this case, you can manage your version in either JIRA side or QuickBuild side. See below page:
http://wiki.pmease.com/display/QB40/Int ... siontoJIRA

Another way I think you may use a more specific string like 1.0.x, and then QuickBuild will append a real 'fix version' to it.

stevenlab · 1 decade ago

our version string is very long like "productname-ver1.0.0.1-buildxyz-comnumber", can this work like 1.0.x? <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" />

steveluo ADMIN · 1 decade ago

Yes, it doesn't matter.

#10

stevenlab · 1 decade ago

that's great! <img src="{SMILIES_PATH}/icon_lol.gif" alt=":lol:" title="Laughing" />

could you please share the match contiditons when qb try to find the jira versions as well? <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" />

#11

steveluo ADMIN · 1 decade ago

I don't know what kind of pattern you want? If you manage version from JIRA side, in configuration setting, just use next unreleased version from JIRA as your build version, no need for any pattern. See the wiki I mentioned.

#12

stevenlab · 1 decade ago

we managed versions in qb not in jira, so I actually want to know:
when release a new version in qb and qb will try to find a "1.0.x" in jira, qb will try to match, so what is the match conditions? <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" />

Thanks a lot!

#13

steveluo ADMIN · 1 decade ago

Hi,
Sorry, I still do not understand. If you manage version in qb, you still needn't any pattern.
I'm afraid that you mis-understand my point. QB cannot replace 1.0.x to an actual version, and can only append the version. That is, after successfully updates the issue, you will notice that both 1.0.x and 1.0.3 exist in 'fix version' field.

When you want to release a new version to JIRA, the release version step will create and release the build version to JIRA automatically, in the meantime, QB will update 'fix version' field for issues with Resolved/Closed status, the issues can be:
[list]
Resolved/Closed issues found in commit messages
Resolved/Closed issues in previous update issue steps
Issues filtered by a specified filter (the filter should be created by the same user as defined in configuration JIRA server setting)
Issues with specified keys
[/list:u]

So, I'm not sure where you want to input the pattern. Please let me know more detailed.

#14

stevenlab · 1 decade ago

Looks like we backed to start...

so is there a possibility to add a new feature for this? <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" />

Thanks!