JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler

NEW : We have got a new blog where we post some interesting SWF internals info.

List of issuesList of issues

#992 Issue Tracker needs the ability to be reset. Label cannot be cleared except by clearing cookies!
Author:
Date created:
Type: question
Visibility: Everybody
Assigned to:
Labels: Site feature
State: closed Help

> What steps will reproduce the problem? Go to Issue Tracker and Select a Label. Then click on 'Filter' > What is the expected output? What do you see instead? First I would expect the results to be the latest, not the ones from 2011, wrongly shown to be Modified on: 05/30/2015, 6:54:50 pm So I click on the 'ID' Header and reverse the index to 'latest' at the top! If I clear the label altogether, then it refuses to remain cleared and returns after I click on another header. Clicking on 'new bugs' again brings results 'topsy turvy', with the ancient ones at the top. OK, so I did not put any 'labels' on my Issues. Can you tell me how this is done? > What version of the product are you using? Is it "nightly build"? Which operating system do you have? > Please provide any additional information below. If the problem is related to a SWF file, attach it here, otherwise we can't help you.
After you clear the label, but before you click on another header you should click on the filter button.
Thanks for the info. How to set labels on an issue?
currently only our developers can set labels - me and honfika. We categorize issues ourselves. It is relatively new feature. Maybe we open this feature to all users or at least issue authors. I would like to have some consistency with the labels. If anybody could add any label then it would be a one big mess. Also many users can't properly recognize which labels are suitable. So there maybe mistakes or wrong used labels. It is easier to add couple labels to an issue by myself than checking whether user placed the labels correctly. It is more feature for us - developers - than for users.
Thanks for your response.
State: new→closed
Type: bug→question