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,317 other followers

Archive for the ‘Issue/Bug tracking’ Category

Jira peculiarity: there is “convert to sub-task” for a Story, but no “convert to task”. TL;DR: use “move” for that

Posted by jpluimers on 2021/04/13

Depending on the issue type, a workflow might be different.

Since for Software projects, the default workflow Story might not be appropriate during the workflow, it makes sense to convert it.

For issue types other than sub-task, the dropdown only has one conversion entry: “convert to sub-task” (a sub-task has only “Convert to Issue”).

In order to convert to other issue types, use the “Move” option. There in the first step, you can change the issue type.


Read the rest of this entry »

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

Jira “Preformatted” is not “Preformatted”

Posted by jpluimers on 2020/12/25

Found out that Jira has its own markdown for issues and comments.

I knew the editor for it has a Style drop down with a “Preformatted” entry.

Initially, pasted text looks preformatted, but after saving the issue or comment, often all or part of that text did either:

  • did not display as preformatted
  • had curly braces around them

A co-worker indicated the plus sign on the right can insert blocks (I thought that while it was next to inserting emoticons, it was for inserting unicode symbols like plus).

Alas, no: it is for adding things that are not symbols at all, and too has a “Preformatted” entry.

For sake of consistency, both “Preformatted” entries produce different markup.

The “Style” entry of “Preformatted” basically surrounds all lines with curly braces, then upon saving tries to do some interpretation and removes parts.

The “Plus” entry of “Preformatted” surrounds a block of lines with {noformat} entries at start of end.

Then there is the “Code” entry under “Plus”. It insert a code block, does not allow you to select the language, but assumes everyone loves programming in Java, as now the surrounding entries are {code:java} at the start and {code} at the end. The default block is this one in “Visual” mode:

// code placeholder

and this one in “Text” mode:

Read the rest of this entry »

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

I really wish people reporting bugs provide more factual details, especially when asked for

Posted by jpluimers on 2020/12/15

Basically the below thread goes like this: [WayBack] GExperts / Bugs / #92 Grep cannot handle UTF-16 and UTF-32 pas files

  1. There is a bug in UTF-16 and UTF-32 handling in your tool when running under AAA, but  not when running your tool under BBB; these files fail: xxx.txt  and yyy.txt
  2. Which version of our tool did you run under AAA and which version of our tool did you run under BBB
  3. It fails with your tool when running under AAA , but succeeds under BBB
  4. Repeat at step 2 until you fall asleep.

Part of the [WayBack] Short, Self Contained, Correct Example are indeed in it, but without more details it is hard to reproduce.

So without the reporter providing those details, nobody, especially not on open source projects, is going to fix it just on that bug report.

Via: [WayBack] It’s time for a gift to all Delphi developers, a new Release of GExperts. Happy Holidays! (But do spend some time with your family rather than testing G… – Thomas Mueller (dummzeuch) – Google+

Which highlights another conceptual problem from the same bug reporter: expecting a new version to have a regression of all open bugs against the new version.

That’s not how the world works, if it has ever worked that way. If your issue is not mentioned in any release notes, then assume nothing happened. If you want to bump it up, then provide more details.


Posted in Conference Topics, Conferences, Development, Event, How to report bugs, Issue/Bug tracking, Software Development | Leave a Comment »

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 »

<span>%d</span> bloggers like this: