-
Notifications
You must be signed in to change notification settings - Fork 16
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
Test og release av v1.3.0 #534
Comments
@tarjeieo #520 should be tested multiple times, with bygg and anlegg projects on a new installtion, and with bygg and anlegg projects where PP365 is upgraded to the latest version. From the issue, I can't see that this has been done, and this is an issue we have struggled with for some time. How can we guarantee that it has been fixed this time? |
#578 OK. Also tested with new user which was added only as member to portfolio level, and then added to "Porteføljeinnsyn" SharePoint group. |
#576 This does not include "how to test", but if it is supposed to look like the included picture where "prosjektstøtte" toghether with the names of the project participants, it seems to be working. @tarjeieo should verify this issue before release |
#526 Tested OK |
#498 Tested OK |
#537 Tested partially OK Avventer is a part of the project properties list, but other than that, it can't be found either as a field on the project properties list on the project home site, or as a filter available in Porteføljeoversikt. I find a new view available for "Avventende prosjekter", but I think it should be included as a field in the properties list on project level as well. |
The view "Avventende prosjekter" is manually created by me in our test environment, and is not part of the product. |
Yes I think it should be, without there is no reference to Avventende prosjekter, which really don't provide the option any value. It should also be visible as a field in the filter list and the project properties view |
You can test further here: https://puzzlepart.sharepoint.com/sites/ProsjektportalenByggAnlegg. The fix was quite intuitive to solve when found (thanks @Petterandre), and I'm quite certain this is good now |
Added "how to test" as a comment. There is an issue with upgrading existing projects, you need to first edit project properties, and after that you will receive the new fields in the project properties. This is something we need to look into/communicate better, but this need to happen after the 1.3.0 release. Feel free to create issue |
Agree that it should be a field in the project columns list, but this is another issue not necessary to include in 1.3.0 |
What does this mean? It's added as an option for a choice field now. What does it mean to add it as a field? |
In the "Prosjektkolonner" list, to have it viewable, filterable in the portfolio |
But that's not related to the Avventer option? Isn't that related to the project status field? |
Indeed! That's why it will be a new issue not related/blockin 1.3.0 |
Testing the new version before creating new release
Checklist for testing the additions, changes and fixes
Version 1.3.0
Testing to be performed on installation in: Puzzlepart tenant
Note to issue creator: Example from changelog (remember to add checkboxes):
Added
Fixed
Changed
After everything has been checked and approved a release of the new version can be created. It is important that the changelog, this issue and the release notes are equal.
Checklist when building a new release
Merge dev to main
Build release
Test the new release from main
Inform
The text was updated successfully, but these errors were encountered: