-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to fetch the details of release note from Release Info section? #895
Comments
The tags are not stored in named fields, but as a comma separated list in the field
|
@rfennell , But my concern is whether is there a way or possibility in which I get to fetch the details or data from Work Items >> Release Info tab where my actual Release Notes related information is available? Is there a tag which can help me here? As per the current setup I am getting the list of Work Items, Title of the WI, Description, ID, etc. but I am more interested towards the details of Release Note to get auto fetched from the WI itself. Kindly let me know if you are familiar with such tags then it can help me in achieving my task. |
I don't think those fields are available as part of the release or work item objects. There is no quick way to check with the PowerShell based task. However if you use the Node based one you can dump the contents of any of the returned objects to see what fields are available. You have a number of of options to help here
So I would dump the object out and look for the field that contains the information you are after. Hopefully it is present |
Thanks for the updates. I migrated to this new plugin "Generate Release Notes (Crossplatform)" and did some modifications in my Azure release pipeline. I am not sure what is wrong here but it doesn't fetch any data in my .md or .htm file which is set as the output. Looking forward for some suggestions or help, appreciate it! |
A few things...
If you still have issue upload the log file and I will have a look |
It is still not working. I am attaching the log file for your reference. |
The log shows that the task has found the build, but there have been no changes e.g. WI, CS or PRs since the last successful build
This is by design. The release notes are what has changed since the last successful build to that branch/stage. As the WIKI details
So if you want to generate changes since some fixed release you can use the |
I think that's not the case because the same logic which is part of https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-GenerateReleaseNotes-Task&ssr=false#overview gives the output and details of all the work items. Anyways this might not help us in achieving the exact requirement of release note details so will think some other way. Thanks for all the support and assistance. |
The old PowerShell version does not make use of the current standard Microsoft APIs to find associated items. It predates the API and uses some very 'interesting' home grown logic - this is why it going to be deprecated. It's behaviour is confusing The Node based task should list the same associated items as the Microsoft UI |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Describe the bug
How to fetch the details of release note from Release Info section?
I want to fetch the information from the Work Items into a Release where I am using the task 'Generate Release Notes for Pipeline Builds or Releases' for generating the release notes.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Need the exact tag for fetching the details from Work Items.
Screenshots


Attached a couple of screenshots for the same.
What is the issue see:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: