v1.0
avatar zero-24
zero-24
12 Apr 2014

Steps to reproduce the issue

  1. Login as user at the JBS Group (with permissions like @wilsonge or @zero-24)
  2. Edit a Issue that not your own (e.g. change status to pending/rtc or other)
  3. save
  4. you get a 404 error.

Expected result

Issue can save and change e.g. the status

Actual result

404 error:
screen shot 2014-04-12 at 13 36 20

System information (as much as possible)

see screenshot.

Browser: FF 28.0
BS: Win

avatar zero-24 zero-24 - open - 12 Apr 2014
avatar wilsonge
wilsonge - comment - 12 Apr 2014

Confirmed
You may blame the J!Tracker Application for transmitting this comment.

avatar elkuku
elkuku - comment - 13 Apr 2014

The issue here is that those actions must be performed by (or on behalf of) an authorized user (or a bot).
In theory this should not be a problem, it's just missing :wink:

I think this is another thingy we have to solve before releasing 1.0 or doing serious stuff.

avatar b2z
b2z - comment - 13 Apr 2014

Yeah, that's a long story #318

avatar elkuku
elkuku - comment - 24 Jul 2014

This has been fixed by #337 but GitHub wasn't able to auto-close this, probably because #337 was auto closed by #389...

avatar elkuku elkuku - change - 24 Jul 2014
Status New Closed
Closed_Date 0000-00-00 00:00:00 2014-07-24 23:18:00
avatar elkuku elkuku - close - 24 Jul 2014
avatar elkuku elkuku - close - 24 Jul 2014

Add a Comment

Login with GitHub to post a comment