We have been keeping an update log in a g-doc and maintaining it manually outside of Jira. The document keeps track of every release and the change notes. Is there a way to automate this in Jira?
Update log example:
7.16.395
• Fix for error when applying stock from schedule tree.
7.16.394
• Part configurations update when templates are selected.
7.16.393
• Fix for subbing multiple order BOM items at once on the Part>Usage tab.
• Fix for inventory counts not syncing.
• Fix for marking order items complete.
• Fixes for pick list quantity calculations and prioritization.
• Template changes updated to part configurations with the 'Sync w/ templates'
you can use Jira Automation for it.
Create an automation rule which will automatically trigger along with a new release.
to do so,
goto project setting
select Automation
Create a new Rule
Select "Release new Version" in the When section
Use lookup issue action and add JQL filters like project='xyz' and fixVersion= '{{release.name}}' .....
finally select a notification action like slack/email or create a wiki page
Tempalte for notification action :
{{#lookupIssues}}
> <{{url}} | {{key}}> : {{summary}}
{{/}}
Let us know if it helps
Related
Whenever there is a new release of an APK, I create a release version under the project
releases option in JIRA. And now, when creating an issue, I put the newly created version
in the affectedVersion field.
But now, when I have to search for all the issues in this version, I have to write a JQL
like project = "BA" and affectedVersion=2.0-uat-2 order BY created DESC
Is there a way to avoid writing this JQL and instead have a dropdown for affectedVersion
which shows all the versions. This way, there will not be any need to write a JQL manually
I've received a request to create a custom report email for our executives. When we do a major release they want a list of Features of that release. What i need to do is read the related Tasks to the release then traverse up parent nodes until i get to the features that are marked with a tag "Executive". My Issue is that I can't find any document on how get the "Work items linked to associated changes".
I've been able to just through to get the specific build
GET http://XXX.MYTFSSERVER.COM/tfs/Collection/Project/e5e632e2-ae70-41c9-9d72-6686d2375f14/_apis/build/Builds/69330
But I don't see any link to get the workitems associated to the build.
Releases already do this out-of-the-box. On the Work Items tab of a release, you can have it generate an email that contains all of the work items associated with that release relative to an earlier release.
There isn't any build-in way to achieve this such as through TFS work item query. You need to build a extension to get all work items of specific release and filter them later.
The steps to achieve that with extension:
Get specify release to get build id
Get work items of that build per build id
Get related work items
Filter the work items which you actually need
A detail simple code of extension to get work items of specific release that you can refer to this link: TFS 2017 Release Management: How to display parent PBI for Tasks under Release
Is there any way to add a new drop down on the bug page in TFS. I want to add a new drop down as 'Bug Fixed In Build' with options as build versions
Thanks
You could add a Integration Build filed for your bug work item type.
When the Integration Build field is present in the WIT definition,
Team Foundation Build identifies work items that were resolved with
each build and then updates those work items to set the build number
in which they were resolved in the Integration Build field.
More detail info please refer this link: Fields that support integration with test, build, and version control
To display the fields in the work item is also not hard in TFS. Details please take a look at this tutorial: Add or modify a work item type. Highly recommend you to install Team Foundation Server Power Tools and use Process Editor to modify the work item template.
Note: To add or customize a WIT, you must be a member of the Project Administrators group or have your Edit project-level information permission set to Allow.
We have JIRA issues with the following fields:
Affects version - version where issue is noticed
Target version - version in which we want to fix the issue
Fix version - version where issue is really fixed
The release planning is based on the fix version, I suppose per default. How could it be changed to use the target version? We set the fix version when closing an issue, so it is not at all appropriate for the planning.
"Affects version" and "Fix version" are system fields in JIRA and various screens are based on them. This is logic that you cannot change.
The "Target version" is not a default JIRA field, so it must have been added as a custom field on your instance.
Instead of trying to change the concept of a "Fix version" you're better of using it as it is intended by JIRA and customising your own logic with custom fields that you add yourself. Otherwise screens like JIRA's "Releases" view will not behave as expected.
So you should use the "Fix version" field to plan the target release and update it with the appropriate version if the actual release changes. For any other kind of version info that you like, introduce your own fields.
In the "Releases" view you can click on "View in Issue Navigator" on the right side:
This will show the JQL that is used by that view and it will show something like:
project = 12421 AND fixVersion = 17740 ORDER BY priority DESC, key ASC
This is hardcoded and I don't know of a way to customise this.
Can we get release information from checkedIN history.
we are using TFS 2012.
we have frequent release mostly on each week or on each 14 days.
Can we generate release document from TFS ?
(something like, based on TFS checked IN comments OR some how )
One way to do this would be to use Work Items (e.g. User Stories and Bugs) to generate your release notes.
But this requires your team to have the discipline to enter the information into TFS that allows it to associate work items with a release. For example:
Require developers to associate change sets with work items
Use fields such as "Iteration" or "Integrated in build" in work items to identify the release to which a work item belongs.
You could then create a suitable Team Query and export it to Excel to generate release notes.
I tend to use the Tf history command line tool to get information of changesets between two particular dates (or changesets). You can pass the /format:detailed parameter to get details such as changes involeed.
For example, the following will list all the changes between the 01/02/2014 & 24/04/2014 and write it to the history file.
tf history /noprompt * /recursive /v:D01/02/2014~D24/04/2014
/format:detailed > C:\history.txt
I like the TFS Changelog tool. Ready to use and easy to integrate.
TFS ChangeLog allows Team Foundation Server (TFS) users to extract information related to Changesets and associated WorkItems into XML format that is transformed into HTML.
All of these are nice tools, but there are a few things still missing I think.
These are technical notes (more like build / history notes) but actual release notes contain more customer friendly items
Not all of the information in TFS are wanted on the customer release notes (internally found bugs vs reported bugs)
As of now I use the TFS Community build manager to generate the technical build notes. It uses OpenXML and works fine for you build notes. It's even easy to create a custom word document for it.
For release notes we actually use the TFS User stories / tasks to be able to query on it. And for now, we create the document manually with the query results. We're looking into creating some tools that might do the following:
Run queries corresponding to the document paragrahs
We have a TFS template field indicating that the work item must be on the customer release notes (but we should change this to use 'special' iterations or so to eliminate the need of a custom field.
Automatically fill in the OpenXml placeholders in the document the same way as the build notes generator does.
Like the TFS Community Build Manager you could create a TFS Community Release Notes Manager that asks for query names and runs these queries to get to the required data.
The main question here is whether there are already tools that do this?
I know this is an old question, but perhaps you can use this task extension Generate Release Notes Build Task (for local TFS or as an extension to VisualStudio.com).
This extension is a build task you can use in build steps. This task generates a markdown release notes file based on a template passed into the tool. Here is an example of release notes output:
Release notes for build SampleSolution.Master
Build Number: 20160229.3 Build started: 29/02/16 15:47:58 Source
Branch: refs/heads/master
Associated work items
Task 60 [Assigned by: Bill ] Design WP8 client Associated change
sets/commits
ID bf9be94e61f71f87cb068353f58e860b982a2b4b Added a template ID
8c3f8f9817606e48f37f8e6d25b5a212230d7a86 Start of the project