For medium and big projects need possibility to delete issues, not empty ptojects ( with all issues), not empty folders, to delete user accounts
What you think about it ?
Hello,
Deleting entire projects and folders is technically possible and could be implemented in a future version.
Deleting users is not implemented on purpose. If a user account was deleted, the name of that user would disappear from the history of issues that were created or modified by that user. Instead, user accounts which are no longer needed can be disabled.
Deleting issues is problematic. When the client application updates the contents of a folder, it only downloads information about issues which were modified since the last update. So if the issue was deleted in the database, it would still remain in the client's cache. It is technically possible to notify the client about deleted issues, but that would mean changing the protocol in a way which is not compatible with earlier versions.
Besides, there is rarely a need to irreversibly delete an issue. It's always better to change its status to "Closed" (or "Invalid", "Obsolete", whatever). You can define a filter which hides those issues from the view, but they can still be accessed or "undeleted" if there is a need.
Well, it's the same problem as with deleting issues - it's not technically possible without breaking the compatibility of the protocol.
Temporary attachments seem like a weird idea, honestly. The idea of WebIssues is to store things permanently, with entire history preserved. If you really need temporary files, you can store them on a network share or FTP server and put links to them in comments or attributes in WebIssues.
>it's not technically possible without breaking the compatibility of the protocol
who needs compatibility with the old protocol if new cool things will be added in new protocol?!
>you can store them on a network share or FTP server and put links to them in comments or attributes in WebIssues
it is not so usable!
for example: i create issues and i want get some examples selectivity to issue from my team. i don't want lost my time with searching/downloading needed files from ftp. i need this examples for first time and i don't want open this attachments anybody else some time later.
Hello,
Deleting entire projects and folders is technically possible and could be implemented in a future version.
Deleting users is not implemented on purpose. If a user account was deleted, the name of that user would disappear from the history of issues that were created or modified by that user. Instead, user accounts which are no longer needed can be disabled.
Deleting issues is problematic. When the client application updates the contents of a folder, it only downloads information about issues which were modified since the last update. So if the issue was deleted in the database, it would still remain in the client's cache. It is technically possible to notify the client about deleted issues, but that would mean changing the protocol in a way which is not compatible with earlier versions.
Besides, there is rarely a need to irreversibly delete an issue. It's always better to change its status to "Closed" (or "Invalid", "Obsolete", whatever). You can define a filter which hides those issues from the view, but they can still be accessed or "undeleted" if there is a need.
Regards,
Michał
Hello, Michał
And what about Deleting attachments?
Or, what you think about Temporary attachments, needed only for some time and auto deleting after it.
With best regards, Igor Davydenko
Well, it's the same problem as with deleting issues - it's not technically possible without breaking the compatibility of the protocol.
Temporary attachments seem like a weird idea, honestly. The idea of WebIssues is to store things permanently, with entire history preserved. If you really need temporary files, you can store them on a network share or FTP server and put links to them in comments or attributes in WebIssues.
Regards,
Michał
>it's not technically possible without breaking the compatibility of the protocol
who needs compatibility with the old protocol if new cool things will be added in new protocol?!
>you can store them on a network share or FTP server and put links to them in comments or attributes in WebIssues
it is not so usable!
for example: i create issues and i want get some examples selectivity to issue from my team. i don't want lost my time with searching/downloading needed files from ftp. i need this examples for first time and i don't want open this attachments anybody else some time later.
make it for me, plz. :)
p.s. sorry for bad english