In Progress
over 3 years ago

Integration to create JIRA items (or requests) from the context of a Website

At the SDL Connect 2016 event, one of the the user group attendees described this use case.

The customer publishes articles online using SDL Web that require subject matter expert (SME) contributions and review.

These SMEs work for the company, however, they are not content authors and are not expected to edit content directly. The team managing the SDL Web setup would like to allow SMEs the ability to submit change requests for published pages to create work for the content organization to prioritize and manage.

The thinking was perhaps these requests could be made using or within Experience Manager, or a similar "in context" user interface.

This particular customer uses JIRA. At the time SDL Web Product Management asked  to look into this and he created this Alchemy extension that connects JIRA-to-and-from-SDL Web:

There were related request made at Tridion Developer Summit 2015 in the GUI extension ideas session. One was for a "JIRA Integration" and another was the ability to pass on all the details of a CM-side issue to an internal IT group or perhaps Support (a feature to recreate the user's context) by

There are different levels to this request:

  • Could there be a point-to-point Connector to JIRA and/or by email so that non-CMS users could request changes to in a website that would then give CMS users work. This first part would actually be more website / JIRA extension than specific to the CMS.
  • Ideally, such an integration would pass on the identifiers on the page (Component Presentation IDs, similar to the Acrolinx Connector) to give editors deep, contextual links to CMS items where links would open the specific Component or Page in the correct Publication.
  • Like all Connectors, maybe this could be generalized for more than this use case (not just JIRA). :-)

Perhaps the links (to email or JIRA) shouldn't be public and the Web application should first handle a request before sending it off, but I'll leave the voting and details to you and the community. :-)