The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,117 other followers

Archive for the ‘Issue/Bug tracking’ Category

Getting rid of bugs: mark them as “new feature” – as cancelling a  THTTPClient.BeginGet() does not work as intended

Posted by jpluimers on 2019/04/24

I have seen this happen before, but it seems to be a habit on the Quality Portal: getting rid of bugs by marking them as “new feature”:

[WayBack] I’m using THTTPClient.BeginGet() to create an async get request to a webservice that holds a connection open until it has data to return (sort of like a… – Brian Ford – Google+. which basically was another person finding out about [RSP-20827] THTTPClient request can not be canceld – Embarcadero Technologies, which got marked (a month after submission!) as “Issue is reclassified as ‘New Feature'”.

I get why it happens (there was something exposed, but some of the functionality is missing a feature which needs to be added).

Marking it as such however sends the wrong signal to your users: we do not see bugs as bugs, so they get on the “new feature” pile with no estimate on when the feature will be done.


Posted in Delphi, Development, Issue/Bug tracking, Software Development | Leave a Comment »

My contributions to RAD Studio – Jose León – Medium

Posted by jpluimers on 2019/02/28

For my link archive, as a reminder to check the Sistel JIRA tool, which is an IDE like tool for JIRA: [WayBack] Business Process Studio for JIRA | Sistel

He has some very interesting posts at [Archive.isJose León – Medium.



Read the rest of this entry »

Posted in Delphi, Development, Issue/Bug tracking, JIRA, Software Development | Leave a Comment »

Text Formatting Notation Help – Atlassian JIRA

Posted by jpluimers on 2014/05/02

Too bad Atlassian don’t specify that the {code} tag now supports more languages.

The trick is to specify an invalid one (like JSON, for which you can use javascript), then it emits an error telling you which languages are supported:


Available languages are: javascript, sql, xhtml, actionscript, none, html, xml, java

(Yes I know there is a JIRA MarkDown plugin, but not every customer installs plugins at will)


via: Text Formatting Notation Help – Atlassian JIRA.

Posted in Development, Issue/Bug tracking, JIRA, Software Development | Leave a Comment »

%d bloggers like this: