[pull] dev from opf:dev #507
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Supports `aria-label` and `aria-labelledby`.
Also switches to using `XPath` DSL - this now generates the following
XPath query:
.//*[(./self::ul or ./self::ol)]
Fix editing issue priorities
https://community.openproject.org/wp/62487 There are two important steps when creating a child through the API: - Update the ancestors attributes based on the child attributes - Update the scheduling of work packages that are related to the child The order is important as the parent will switch to automatic mode if it has no predecessors and gains its first child. The switch to automatic mode must occur before rescheduling. Previous code was buggy because the rescheduling happened first: the parent was still in manual mode and so its dates were not updated. Also fixed some other unit tests which were invalid (doing assertions on the wrong objects.)
…misaligned-when-populated-with-data [62249] Many WP fields are visually misaligned when populated with data
Previously we would have "fallen out" of the JWT strategy, even though the token was clearly intended to be handled by this strategy. For my configuration this led to the final error message being generated by the Basic auth strategy, leading to a wrong error message.
…should-update-parents-dates [62487] Fix rescheduling when creating a child through API
Service accounts are intended to be special users that are not explicitly manageable through the users UI (just like "System" and the like), but are intended for identification of "services", not real people. The initial scope of this will be to allow authentication of SCIM clients, that will be able to provision users into and out of OpenProject. However, the general idea is to allow using service accounts for generic application-to-application communication as well. Given proper permissions and scopes (i.e. api_v3), it would also be possible to use a service account for requests against our normal APIv3.
…n-relations-tab [#61885] Sort relations in relations tab by created_at
JWT: Allow authentication through client credentials
* Introduces the AMPF series of tests * Adapts to the new API * Incorporates feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )