Hi Shawn, Ok, I will use Jira next time. I was just being too lazy. I have forgotten my Jira password and didn¹t want to go through all the hustle of restoring it and creating issues :)
Coming back to the permissions, I have create a ticket for it with a detailed description and screenshots: https://issues.apache.org/jira/browse/FC-100 By the way, I do not know if it is possible in Jira to give users rights to modify issues created by them, but it definitely would be something useful. /Oleksandr On 1/5/2015 06:11 , "Shawn McKinney" <[email protected]> wrote: > >> On Apr 30, 2015, at 10:02 AM, Oleksandr Bodriagov (Polystar) >><[email protected]> wrote: >> >> I have 4 problems with fortress-web. >> Problem #1: >> I wanted to add two permissions using fortress-web, but it didn¹t work. >> Permission 1: >> - Object Name = https://galileo/blabla >> - Operation Name = GET >> - Roles = myreader >> Permission 2: >> - Object Name = https://galileo/blabla >> - Operation Name = POST >> - Roles = myreader >> >> I got two POST permissions instead. >> > >Did you add https://galileo/blabla as object to the Perm Object Page >first? Once you do that, you can use the object name as a reference in >the permission page for your get and post. I tested to make sure and it >worked fine on my machine. > >> >> On Apr 30, 2015, at 10:02 AM, Oleksandr Bodriagov (Polystar) >><[email protected]> wrote: >> >> Problem #2: >> Role¹s temporal constraints End Date 09/01/2111 is shown as 21110801 in >>the role list/table. >> >> Problem #3: >> Roles defined via fortress-web lose Begin Time in the table view after >>modifying lock dates. >> >> Problem #4: >> Modification of Begin Date (or Begin Time) leads to the month change in >>Begin Lock and End Lock. >> > >Good catches! I have made a couple of changes that should help. Can you >do another git pull on your fortress-web and try again? > >Here¹s the issue we¹ve created: > >https://issues.apache.org/jira/browse/FC-98 > >Thanks > >Shawn >[email protected]
