Entries Tagged as 'bugbase'

We would like to inform you that we have moved to a new bug tracking and reporting application called “Tracker". This was necessary as internally at Adobe, we have now transitioned to JIRA for issue/bug tracking for all the products. While functionally Tracker is similar to the BugBase application, there are still few inherent differences, that we thought, we should highlight. The same have been listed below:

1. While logging a bug, you will see a field, Component, which is equivalent to Product Area in BugBase. Any Component in Tracker is a combination of Product Area: SubArea, for example, Administrator: Admin API, Administrator: Code Analyser.

2. You will also see fields "Status, Resolution & Reason Code", which is equivalent to BugBase’s "Status, State & Reason".

3. 'Duplicate ID' for any old bugs would be seen as a part of 'Bug Description'.

4. Voting comments for old bugs would not be seen. However, count of votes is visible for all the old bugs.

There are some issues with Tracker that we are currently working on . While using Tracker, you may face:

  • Issues in receiving mail notifications for any change in a bug.
  • Some discrepancies in the number of bugs, that you had logged or voted for.
  • Some discrepancies in the number of comments in the bug(s).
  • The field “Reported By” for all bugs is missing.

As always, we request you to test drive our new bug tracking system and send your valuable feedback, so that, we can enhance the overall user experience. We will keep you posted once we fix the issues listed above.

 

We acknowledged at CFSummit that we need to move the needle when it comes to bug fixes in the product. Just as we had announced, we are making improvements in this axis.

Here are some of the highlights so far.

A total of 423 legacy bugs (legacy bugs are those that were reported in previous versions starting from ColdFusion 11) were resolved as a part of the release.

A total of 95 external bugs were fixed in just update 1 and update 2 for ColdFusion 2016. More details about what fixes went in update 2 can be found in this post.

The average age for bugs to be verified by the product team from the time it is logged in the system is now down to 4 days. This was around 35 days during the ColdFusion 11 timeframe. This gives you a good sense of comparison between where we were and where we are headed towards.

Also, the upcoming update 3 promises to be an even significant update in terms of bug fixes when compared to update 1 and update 2. Stay tuned to hear about the upcoming update. 

I want to leave you with the message that we are monitoring our improvements in this space very closely. You will hear more details about our overall improvements to bug fixes at CFSummit this year. We look forward to seeing you there!

 

I am very excited to announce the availability of new public bugbase for ColdFusion that is built using ColdFusion. Here is the link. - The bugbase currently supports logging bug for ColdFusion Builder 2. - We are in the process of migrating old bugs to new bugbase and they should appear in some time. - You need to use search option to find/list bugs A big thanks to Vinu, Kunal, Manju and other folks on the CF/Watson team to make it happen.