Bug 1236199 - Allow external trackers to point to internal customer case management attachments
Summary: Allow external trackers to point to internal customer case management attachm...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Bugzilla
Classification: Community
Component: Attachments/Requests
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On: 1239083
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-26 19:41 UTC by Jeremy West
Modified: 2025-10-16 23:41 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-23 23:44:57 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeremy West 2015-06-26 19:41:22 UTC
CEE would like to be able to link to customer data in the external trackers section using the URLs provided to customer case teams via SFDC.  This will allow us to keep customer data protected since these URLs require authentication.  I've provided a sample URL below.

https://api.access.redhat.com/rs/cases/01446406/attachments/b21a222f-a20e-4292-8b43-8b049cc498dc

Comment 1 Matt Tyson 🤬 2015-07-17 01:42:06 UTC
Jeremy:  The URL looks like it has two components to it.

1) 01446406
2) b21a222f-a20e-4292-8b43-8b049cc498dc

The external tracker code can only handle a single unique identifier for external URLs.

Is it possible to access the attachment with a single identifier?

Comment 4 Mike Moore 2015-07-31 11:51:22 UTC
I think Tom is the best person to speak to this.

Comment 5 Tom Butt 2015-07-31 13:36:26 UTC
There isn't a way to do that right now.  As we're constantly talking about an attachment redesign, I would like to make sure we take that into account for future work, but don't know that it's an effort we should do in the meantime (although I don't fully understand the impact this currently has on the "external tracker" or how that's maintained.

Comment 6 Jeff Fearn 🐞 2017-07-04 12:59:08 UTC
Just a note that this can be done ATM as long as you have a base URL for the ET and use the variable parts as the ID, like we do for polarion.

e.g. If you had a tracker that had the base as "https://api.access.redhat.com/rs/cases/" then the ID would be "01446406/attachments/b21a222f-a20e-4292-8b43-8b049cc498dc" which isn't visually stimulating but is functional.

Comment 7 Jeff Fearn 🐞 2018-07-31 11:37:48 UTC
Is this still required? If so take a look at [1] and tell me if that is OK?

1: https://grok.usersys.redhat.com/~jfearn/bugzilla/devel-5.0-2/show_bug.cgi?id=1236199#external_bugs_table

The layout in the ID is a configuration setting and can be changed anytime. You just paste the full URL in to the URL field to create the link.

We could set up the ET now and add the ID filter in the bZ5 upgrade.

Comment 8 Jeff Fearn 🐞 2019-01-23 23:44:57 UTC
In preparation for entering maintenance mode we are closing bugs that have been blocked on user need info for an extended period. If you are still interested in this feature request please reopen the bug and provide the requested information.


Note You need to log in before you can comment on or make changes to this bug.