This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
  • Home
  • Advisories
    • SecurID
    • SecurID Governance & Lifecycle
  • Documentation
    • SecurID
      • Authentication Agents
        • API / SDK
        • Apache Web Server
        • Citrix StoreFront
        • Epic Hyperdrive
        • IIS Web Server
        • MFA Agent for macOS
        • MFA Agent for Windows
        • Microsoft AD FS
        • Microsoft Windows
        • PAM
      • Authentication Engine
      • Authentication Manager
      • Authenticators
        • iOS and Android
        • macOS
        • Windows
      • Cloud Authentication Service
      • Hardware Appliance
        Component Updates
      • Hardware Authenticators
        • DS100 Authenticators
        • SID700 Authenticators
        • SID800 Authenticators
      • Integrations
      • SecurID SDK
      • Software Tokens
        • Android
        • iOS
        • macOS
        • Token Converter
        • Windows
    • SecurID Governance & Lifecycle
    • Technology Partners
  • Downloads
    • SecurID
      • Authentication Agents
        • API / SDK
        • Apache Web Server
        • Citrix StoreFront
        • Epic Hyperdrive
        • IIS Web Server
        • MFA Agent for macOS
        • MFA Agent for Windows
        • Microsoft AD FS
        • Microsoft Windows
        • PAM
      • Authentication Engine
      • Authentication Manager
      • Authenticators
        • macOS
        • Windows
      • Cloud Authentication Service
      • FIDO Management Service
      • Hardware Appliance
        Component Updates
      • Hardware Authenticators
        • SID800 Authenticators
      • Integrations
      • Software Tokens
        • Android
        • iOS
        • macOS
        • Token Converter
        • Windows
    • SecurID Governance & Lifecycle
  • Community
    • SecurID
      • Blog
      • Discussions
      • Events
      • Idea Exchange
      • Knowledge Base
    • SecurID Governance & Lifecycle
      • Blog
      • Discussions
      • Events
      • Idea Exchange
      • Knowledge Base
      • Tech Hub
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Ideas & Suggestions
      • Community Support Articles
      • Community Support Forum
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Education
    • Blog
    • Browse Courses
      • SecurID
      • SecurID Governance & Lifecycle
    • Certification Program
    • New Product Readiness
    • Student Resources
Sign In Register Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements

RSA Customer Advisory: Authentication Manager 8.7 P3 re-releasing on March 27, 2023

View Details

Community Ideas & Suggestions

Drive innovation and crowdsource improvement by submitting enhancement requests for the community.
  • RSA Community
  • :
  • Support
  • :
  • Community Support
  • :
  • Ideas & Suggestions
  • :
  • Create a Bug Tracking version of the Idea Exchange
  • Options
    • Subscribe to RSS Feed
    • Mark as New
    • Mark as Read
    • Bookmark
    • Subscribe
    • Printer Friendly Page
    • Report Inappropriate Content

Create a Bug Tracking version of the Idea Exchange

18 Likes
Status: Under Review Submitted by JoyVanBuskirk Frequent Contributor on ‎2017-11-21 01:53 PM

Support is telling me that they are unable to classify issues as bugs. Everything is an enhancement request and enhancement requests need to be logged through the exchange. If that's the new process, I'd like to see the exchange split into true enhancements and bug fix requests. Then we could search all bug fix requests ourselves when troubleshooting issues and up-vote the bugs that are most painful to us so that its clear which need to be fixed first. Workarounds could also be added to the comments for the next person who searches the issue. Under this approach we wouldn't have to weed through true enhancement requests and bug fixes wouldn't have to compete for votes against true functionality enhancements.

Tags (14)
  • Tags:
  • Archer
  • defects
  • idea
  • ideas
  • ideation
  • RSA Archer
  • RSA Archer Suite
  • rsa ideas
  • RSA Link
  • RSA Link Idea
  • RSA Link Platform Idea
  • RSA Link Platform Suggestion
  • RSA Link Suggestion
  • Suggestion
Share
6 Comments
NathanielWallwo
NathanielWallwo Beginner
Beginner
‎2017-11-28 12:17 PM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Report Inappropriate Content
‎2017-11-28 12:17 PM

I think this article does a good job of explaining why this matters:  Brad Appleton's ACME Blog: Bugs versus Enhancements 

LouisHebben
LouisHebben Valued Contributor
Valued Contributor
‎2018-09-07 10:43 AM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Report Inappropriate Content
‎2018-09-07 10:43 AM

My understanding is bugs should be support requests not enhancement requests.  Support requests confirmed as bugs get IDs assigned "ARCHER-xxxx" that can be referenced in release notes.  When we are given bug ID we enter it into our request tracker then check release notes to see when/if fixed.

ScottHagemeyer
Historic Contributor ScottHagemeyer Historic Contributor
Historic Contributor
‎2019-10-03 12:33 PM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Report Inappropriate Content
‎2019-10-03 12:33 PM

Joy VanBuskirk, Louis Hebben, Nathaniel Wallwork, et al.:

 

Does the launch of the new Engineering Requests portal solve this problem?

 

https://community.rsa.com/community/products/archer-grc/blog/2019/10/03/launching-engineering-requests-management-portal 

LouisHebben
LouisHebben Valued Contributor
Valued Contributor
‎2019-10-03 01:30 PM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Report Inappropriate Content
‎2019-10-03 01:30 PM

This is great step, support engineer showed us this morning.  Lets us easily monitor issues we have submitted.

JoyVanBuskirk
JoyVanBuskirk Frequent Contributor
Frequent Contributor
‎2020-01-13 10:34 AM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Report Inappropriate Content
‎2020-01-13 10:34 AM

Hi Scott, Sorry I just saw this. I'm not sure that this is the solution as engineering requests are only opened when support will admit that something is a bug. I had a scenario a few years back where Archer spawned 26 million calculations from a single data import in order to update 7,000 records. It clogged up my system for days until I finally deleted all of the duplicate calc jobs via direct SQL. When I explained the situation to support and asked them to log it as a bug to be fixed, they said that everything was working as designed and I should submit an enhancement request if I'd like things to function differently. If I remember correctly, when I originally posted this idea, I had just spoken to support and been told that the idea of bugs had been done away with and everything was now enhancement requests. In my mind, enhancements are things where we'd like to see new functionality. Bugs are things where the existing functionality isn't working properly. I get it that there can be a gray area between user expectations vs engineering expectations. And sometimes a thing can look like poor design to one person and look like solid design but limited feature set to someone else. But resolving that ambiguity by eliminating the concept of bugs doesn't seem like the solution. That said, I suspect that this isn't even an issue anymore. I work very rarely with support anymore, but the last time I read the platform release notes, I saw that there were separate sections for bug fixes and enhancements and there was a dedicated spot for known issues. So my guess is that the idea of doing away with bugs was a short lived experiment.

rsalinkadmin
Administrator rsalinkadmin Administrator
Administrator
‎2021-08-12 07:26 PM
  • Mark as Read
  • Mark as New
  • Bookmark
  • Permalink
  • Print
  • Report Inappropriate Content
‎2021-08-12 07:26 PM
Status changed to: Under Review
 

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

  • Comment
Completed Ideas
  • RSA Link "Your Content"

  • Logs delivery

View All ≫

Idea Statuses

Proposed 33
Information Requested 1
New 6
Duplicate 1
Approved 1
Already Offered 1
Powered by Khoros
  • Blog
  • Events
  • Discussions
  • Idea Exchange
  • Knowledge Base
  • Case Portal
  • Community Support
  • Product Life Cycle
  • Support Information
  • Customer Success
  • About the Community
  • Terms & Conditions
  • Privacy Statement
  • Provide Feedback
© 2023 RSA Security LLC or its affiliates. All rights reserved.