Migration of ColdFusion BugBase to Tracker(JIRA)

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.


53 Responses

  1. Thanks for your work on the new tracker guys. Out of curiosity since you’re moving to JIRA, is there a reason you couldn’t just expose JIRA directly since it already has a familiar interface with all the features you need. You could still lock it down via permissions for the default users and have internal projects that noone could see. One reason why I can’ think of that you might have avoided that was paying for the per-user JIRA licensing costs.

  2. Hi Suchika,

    Thanks for blogging this. I will add my feedback here.

    Old Tracker says:
    You have logged 609 Bugs and/or Features
    You have voted on 398 Bugs and/or Features

    New Tracker says:
    Issues you have created: 39
    Issues you have voted for: 11

    Old Tracker says: “Please be advised that this website is now read-only and will be shut down soon.”

    Umm! *PLEASE* do not take the old tracker down until all issues, such as this, are fixed.


  3. Good point Aaron. I would add to that, please don’t take the old tracker down at all, but put 301 redirects on each ticket to the ticket in the new system. There are many many links on the Internet that will be around for years to come pointing to the old tracker. It would be really nice if all those links continued to seamlessly work and redirect to the current location of the bug for a long time to come.

  4. “Voting comments for old bugs would not be seen.”

    They should remain seen. I already have bugbase.adobe.com (tickets/comments/votes/status changes/etc) stored to db. Is it okay if I add a comment on each tracker.adobe.com ticket containing its vote comments from bugbase.adobe.com?


  5. Hi Adobe,

    Ticket detail page should also: 1) have name of product (ex: ColdFusion) and 2) say “Bug” or “Feature”.

    bugbase.adobe.com had, for example, “ColdFusion x.x – Bug xxxxxxx” or “ColdFusion x.x – Feature xxxxxxx” at the top edge of each ticket.

    tracker.adobe.com simply has “CF-xxxxxxx” at the top of each ticket, and has “Version: x” under Details.

    1) Change “CF-xxxxxxx” at the top of each ticket to “ColdFusion x.x – Bug xxxxxxx” and “ColdFusion x.x – Feature xxxxxxx”.
    2) Remove “Version: x” from under Details section.


  6. Hi Adobe,

    Here is some feedback regarding the “FAQ” (https://tracker.adobe.com/static/assets/AdobeTrackerFAQ.pdf):

    Just CTRL+F the FAQ for the following strings.

    1) please chose the appropriate value

    Note: “chose” should be “choose”

    2) “Launch Build X.

    Note: It’s missing the ending quote (“)

    3) You can track progress of the bug through the comments updates[..]

    Note: “the comments updates” is not proper. Suggestions: “the comments” or “the comment updates”

    4) If you have regrets about your vote comment you can update your comment or delete it all together.

    Question: How do we edit/delete our comments?

    5) the different Statues of a bug or feature

    Note: “Statues” should be “Statuses”

    6) because of the amount of work it is estimated to fix it

    Note: “it is” should be “that is”

    7) In case your bug is closed as a duplicate, you can visit your bug and click on the bug ID next to ‘Duplicate ID’.

    Note: The “Duplicate ID” links need to be added. This was a useful feature of bugbase.adobe.com. Duplicate IDs should be added as comments on the ticket. The “Details” section of the ticket should contain the clickable duplicate ID.

    8) Due to privacy reasons only external users’ “screen name” is displayed on the bugs.

    Note: I see full names, not screen names. Might want to look into this one.

    9) Please select the Product as “Adobe Tracker”

    Question: Do you mean “Tracker Sandbox”? The “Add Bug” form’s “Product” menu lists “Tracker Sandbox” (not “Adobe Tracker”).


  7. Oops, typo in my “Dec 15, 2016 at 2:03 AM” comment.

    This: “Duplicate IDs should be added as comments on the ticket.”

    Should’ve been this: “Duplicate IDs should not be added as comments on the ticket.”

    To clarify: The formal “Duplicate ID” feature should be added to tracker.adobe.com.


  8. Some notes:

    – Searches using “Reported By” do nothing (probably related to known issue #4 as mentioned by OP)
    – Comments are sorted the other way around vs the old Bugbase
    – In the search result, bugs open in a new tab (If I want that, I can hold ctrl when clicking a link)
    – Search form doesn’t save previously chosen product.
    – Agree with the points made on just using the JIRA UI and the 301s.
    – No more CAPTCHA, yay!
    – Would love a way to filter on all non-fixed issues. So a combination of all open states (like To Fix, Open, To Track, maybe even “Closed+Won’t Fix” since that could still be an open bug depending on the reason for not fixing it)


  9. Hi Adobe,

    On ticket CF-4186779, Carl’s and my names were changed to “External User”. Also, I cannot add a comment on that ticket.

    Please tell me that is a broader issue that is being fixed.


  10. Hi Adobe,

    Tracker forgets the currently-viewed page, upon login.

    Please try these steps:

    1) Logout of Tracker (if currently logged-in)
    2) View any ticket (ex: https://tracker.adobe.com/#/view/CF-4186779)
    3) Login (use case: you are a public user wanting to add a comment or vote)

    Actual result: After login, tracker redirects you to the Tracker “Home” page

    Expected result: After login, tracker redirects you to the page you were on in step #2 (just like bugbase.adobe.com did)

    Hopefully the expected result can be implemented. The current behavior is a bit annoying.


  11. “Voting comments for old bugs would not be seen.”


    On November 10, 2011, voting comments were migrated to bugbase.adobe.com from the previous tracker.

    Example: Please see https://bugbase.adobe.com/index.cfm?event=bug&id=3039641

    See all those comments dated Nov 10, 2011?

    The same migration needs to be done now. All voting comments need to be migrated from Bugbase to Tracker. Bugbase contains MANY voting comments containing important information, and they should not vanish.


  12. Hi Aaron/Mingo,

    Thanks a lot for all the issues that you have reported . We have logged bugs on Tracker for almost all the issues that you have reported .

    1. Difference in count of bugs that you voted or logged : https://tracker.adobe.com/#/view/TKR-18

    2.Bug Submission Failed : This has been resolved .

    3.Unable to edit Vote Comments: https://tracker.adobe.com/#/view/TKR-30

    4.Ticket detail page is missing the “Date Created”. – This has been resolved .

    5. Voter’s name not seen below comment for bug CF-3680177 : https://tracker.adobe.com/#/view/TKR-20

    6.Searches using “Reported By” do nothing : https://tracker.adobe.com/#/view/TKR-31

    7. Comments are sorted the other way around vs the old Bugbase : There is a button using which you could reverse the order.

    8. Search form doesn’t save previously chosen product. : https://tracker.adobe.com/#/view/TKR-32

    9. Would love a way to filter on all non-fixed issues. So a combination of all open states (like To Fix, Open, To Track, maybe even “Closed+Won’t Fix” since that could still be an open bug depending on the reason for not fixing it) : https://tracker.adobe.com/#/view/TKR-33

    10. On ticket CF-4186779, Carl’s and my names were changed to “External User”. Also, I cannot add a comment on that ticket. : https://tracker.adobe.com/#/view/TKR-27 (This bug is not be visible to you now , we will make this visible to you asap.)

    11. Tracker forgets the currently-viewed page, upon login : https://tracker.adobe.com/#/view/TKR-34

    12. Voting comments for old bugs would not be seen. : We are fixing this.

    I may have missed some of the issues that you guys have reported . For any such issue , you can go to Tracker and log a bug against the Product Adobe Tracker [TKR]. Thanks a lot for your feedback and we are trying our best to resolve all the issues .

    – Suchika.

  13. All – Thanks for all the feedback. All critical issues will be addressed on priority. Few issues, from what we are given to understand, will roll out in an update to the tracker application, expected sometime in Feb or earlier next year. Please keep the feedback pouring in!

  14. Can someone please remove the Adobe Coldfusion summit 2016 advertisement on the top of the Blog? It is a bit disheartening to still see it there 2 months after the event took place. Anyone else spot it, read it or report it? Sad.

  15. Hi Adobe,

    Regarding “Issues in receiving mail notifications for any change in a bug.”

    Please make resolution of that issue the highest priority.

    On TKR-18, Adobe asked me for input, but I never got a notification. It wasn’t until an Adobe representative emailed me directly that I knew I was being asked for input on that ticket.

    If we do not get a notification, and thus do not follow-up on a ticket, then Adobe puts a comment such as “No response from customer” and then closes the ticket.


  16. Hi Vamsee and Suchika,

    Thanks very much for logging those tickets and considering our inputs!

    PLEASE do not close bugbase.adobe.com for a while. Tracker.adobe.com is slow and clunky to navigate and is plagued with issues.


  17. Hi Adobe,

    bugbase.adobe.com has an “Awaiting Response” section on the Home page, which, for me, lists ticket 4175138. But tracker.adobe.com doesn’t have that same “Awaiting Response” section. (I will follow-up on 4175138, BTW, and it’s still very much an issue). But.. can you pls add the “Awaiting Response” section to tracker.adobe.com?


  18. Hi Adobe,

    Please see my comment on TKR-18:

    It took me 1 minute and 5 seconds to navigate to the end of the “Created” table, b/c each “Get next 100” button took 14-17 seconds to show me the next chunk of 100 tickets. I *think* I clicked it 6 times. But, when I got to the end, I wasn’t sure exactly how many times I’d clicked “Get next 100” (tired, sry). And the UI doesn’t tell me which chunk-of-100 tickets I’m looking at. Can you please add counters so that we can see how many tickets we filed or voted on? And can you please remove the “Get next 100” buttons? There’s plenty of horizontal space to list all the numbered pagination buttons. And we can’t even sort the columns in the result set. This is currently a tedious UI.

    OH! So another issue.. copy/paste stripped-out the blank lines. If you view my same comment on TKR-18, you’ll see it’s not all jammed-together like it is above 🙂 And copy/pasting comments from bugbase.adobe.com doesn’t do that – it retains the blank lines.


  19. Hi Suchika (or anyone at Adobe),

    Can I please ask you a question? Can I ask you to please pretend that you are an Adobe customer. And pretend you have filed hundreds of tickets, and voted on hundreds more. And pretend you want to communicate with Adobe on many of these tickets. Would you be frustrated if you did not get notifications whenever Adobe replied on a ticket? I know that I am. It’s a highly ineffective way to communicate when there is simply a lack of communication. That is why I am not using tracker.adobe.com very much. I am, first and foremost, waiting for Adobe to fix this:

    Issues in receiving mail notifications for any change in a bug.

    That is the NUMBER ONE issue that needs fixed, IMHO.

    This forum post was created December 14th, 2016. It is now January 27, 2017. Still tracker.adobe.com does not notify us when comments/votes are added on tickets.

    I hope Adobe can make this an Executive Priority to fix the tracker.adobe.com notifications.


  20. @ Aaron & @ Charlie thanks for your feedback . We have forwarded your request to concerned team and also logged bugs for them.

    1.Awaiting Response Section in Tracker – https://tracker.adobe.com/#/view/TKR-69

    2.Date of the Vote Comment appears as the date on which bug was created. – https://tracker.adobe.com/#/view/TKR-70

    3.A button to order Vote Comments – https://tracker.adobe.com/#/view/TKR-71

    4.The front page of Tracker does not explain that we need to add cf- (for cf bugs). – https://tracker.adobe.com/#/view/TKR-72

    5.Attempt to go to bug link re-directs to home page after login – https://tracker.adobe.com/#/view/TKR-9


  21. Hi Adobe,

    I would really love to give feedback on the many CF/B tickets and bug fixes. I find that fun 🙂 However, tracker.adobe.com has so many UI issues and does not send us notifications when users comment/vote. I find that stressing 🙁

    Could we please get a status update on the progress of resolving all the tracker.adobe.com issues?


  22. Charlie’s comments were deleted.
    Please see our comments, where we refer to comments Charlie made:
    Aaron Neff on January 4, 2017 at 11:48 pm
    I agree 100% with every point and suggestion Charlie made.
    Vamsee on January 8, 2017 at 8:58 pm
    @Charlie, this is great feedback! We will raise this with the concerned team and share an update here.
    Suchika Singh on January 31, 2017 at 11:01 pm
    @ Aaron & @ Charlie thanks for your feedback .
    Ameya on March 16, 2017 at 2:33 pm
    Hi Charlie, Could you please let us know which product you tried to file a bug against, in order to help us find the source of the issue.
    However, all of the comments Charlie made were deleted.
    Please do not delete our comments. Please restore Charlie’s comments.

    • Thanks for that, Aaron. Yes, it’s so very odd. And it’s not just on this post but indeed on all posts in the old blog, it seems. It of course feels very specifically targeted, since it doesn’t appear to have happened to anyone else’s. And I noticed it the very first day, and pointed out in one of the first comments on the new blog. Sadly it remains a situation, and yet with no reply.

      I can say (to any who may be wondering) that it’s not like I said something in some post (just before the old blog went down) which was somehow a trigger for any of this. I was simply responding to comments and entries like I always have.

      I do hope that this is resolved soon, and while I hope as well it didn’t happen to comments from any other folks, it would surely be dismaying to find that it somehow intentionally happened only to mine.

  23. Hi Adobe,

    Most of the tickets we’ve discussed have not been fixed. I am waiting on fixes for these tickets (which includes a few we haven’t discussed):

    TKR-10 “”Reported by” field should be visible when viewing bug”
    TKR-15 “Duplicate bug information missing”
    TKR-18 “Number of bugs external users involved in count incorrect”
    TKR-20 “Voter’s name not seen below comment”
    TKR-27 “Comments in Tracker appear to be owned by External User”
    TKR-30 “Unable to edit or delete Vote Comments”
    TKR-31 “Searches using “Reported By” do nothing”
    TKR-32 “Search form doesn’t save previously chosen product.”
    TKR-33 “Add a way to filter on all non-fixed issues. also filter on combination of all open states(Open/To Fix)”
    TKR-58 ” should display bug title”
    TKR-63 “Lines don’t wrap”
    TKR-64 “Make newest-on-top the default for issue comments.”
    TKR-65 “Can’t sort issues on homepage”
    TKR-69 “Awaiting Response Section in Tracker”
    TKR-71 “A button to order Vote Comments”
    TKR-80 “When running a new search, the results default to the page selected in the last search”
    TKR-85 “Vote names/dates hidden”
    TKR-86 “Link to former Adobe BugBase is broken”
    TKR-92 “Search functionality: change single-option selects into multiple-selects”
    TKR-93 “Should not have to select “system” when creating a bug”
    TKR-94 “Version, Component and Found in Build should not be reqd information on the add bug form”
    TKR-95 “”Add Bug” button unreachable on “tablet” view”
    TKR-139 “Vote comments not visible”
    TKR-141 “Can’t search for “null” in title”
    TKR-146 “tracker.adobe.com ticket heading should be useful, like it was in bugbase.adobe.com”
    TSBX-143 “State/Status/Reason no longer related”
    TSBX-144 “search result columns not sortable”
    TSBX-145 “pagination clunky”
    TSBX-146 “bug detail area does not line wrap”

    I’ve added comments on some of the above. Please read my comments.

    Please prioritize these 3 tickets:
    – TSBX-143 (The State/Status/Reason relationships are broken, which greatly impairs searching, and need fixed ASAP)
    – TKR-15 (Tickets need a proper/formal “Duplicate ID” field)
    – TSBX-145 (The “Get Next 100” buttons impair navigation, and need to be removed)


  24. Continuing the conversation w/ myself..

    Added comment on TKR-15 (the Duplicate ID ticket):
    In search results, when Reason=Duplicate, the word “Duplicate” could be a link to the ticket that it’s a duplicate of. That way we don’t even have to read thru duplicate tickets, we can just jump straight to the original.


  25. 7 months in and:

    We’re unable to see all tickets.
    We’re unable to see all vote comments.
    We’re unable to see ticket authors.
    We’re unable to see vote dates and authors.
    We’re unable to see migrated comment authors.

    Please prioritize:

    Add “Reported By” field to tickets: TKR-10
    Migrate unmigrated tickets: TKR-150
    Unhide migrated vote comments: TKR-139
    Add name to migrated vote comments: TKR-85 & TKR-20
    For comment-less votes, display name/date: TKR-85
    Fix author info on comments: TKR-27

    Before we worry about UI, we need to ensure the search result JSON has full and correct data.


Leave a reply