Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
lyskom-server-ceder-1616-generations-topgit
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Per Cederqvist
lyskom-server-ceder-1616-generations-topgit
Commits
cffeafe4
Commit
cffeafe4
authored
Sep 30, 2001
by
Per Cederqvist
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
No showstoppers left.
parent
f50d42d5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
13 deletions
+17
-13
TODO
TODO
+17
-13
No files found.
TODO
View file @
cffeafe4
...
...
@@ -3,19 +3,7 @@ server.
* Showstoppers
** Who is allowed to remove an faq-text-aux-item? 6024603.
Added owner-delete parameter to aux-item definition as this is a
somewhat more general problem. It is getting obvious that the
original code for handling access to aux-items is getting stretched
beyond its limits. The code could stand a complete rewrite that
would allow for detailed control of access to items depending on
the type objects they are attached to.
** Add test cases for recent changes:
Delete aux-item with owner-delete when creator, owner, supervisor
of creator, supervisor of owner, ENA, and someone else.
None!
* Unsorted.
...
...
@@ -491,6 +479,22 @@ server.
* Fixed
** Who is allowed to remove an faq-text-aux-item? 6024603.
Added owner-delete parameter to aux-item definition as this is a
somewhat more general problem. It is getting obvious that the
original code for handling access to aux-items is getting stretched
beyond its limits. The code could stand a complete rewrite that
would allow for detailed control of access to items depending on
the type objects they are attached to.
DONE by byers --ceder
** Add test cases for recent changes:
Delete aux-item with owner-delete when creator, owner, supervisor
of creator, supervisor of owner, ENA, and someone else.
DONE --ceder
** New predefined aux-items: 31-32, 10100-10104: implement them.
DONE --ceder
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment