US 12,141,755 B2
Displaying content in a collaborative work environment
WaiYee Loo, Sydney (AU); Benjamin Edwin Morgan, Sydney (AU); Albert Kavelar, Sydney (AU); and Bree Davies, Sydney (AU)
Assigned to ATLASSIAN PTY LTD., Sydney (AU); and ATLASSIAN US, INC., San Francisco, CA (US)
Filed by Atlassian Pty Ltd., Sydney (AU); and Atlassian Inc., San Francisco, CA (US)
Filed on Feb. 17, 2021, as Appl. No. 17/177,886.
Prior Publication US 2022/0261761 A1, Aug. 18, 2022
Int. Cl. G06Q 10/00 (2023.01); G06F 3/0482 (2013.01); G06F 9/445 (2018.01); G06F 16/903 (2019.01); G06Q 10/10 (2023.01); H04L 9/40 (2022.01)
CPC G06Q 10/103 (2013.01) [G06F 3/0482 (2013.01); G06F 9/445 (2013.01); G06F 16/90335 (2019.01); H04L 63/0815 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method of displaying secure content stored by an issue tracking system of a collaboration work environment within a secure page stored by a documentation system of the collaboration work environment, the method comprising:
receiving, at a first host server executing a first backend instance of the documentation system, from an instance of a client application providing frontend functionality of the documentation system, the client application executing at a client device operated by a user of the documentation system, a first secure content request:
identifying the secure page stored by the first host server; and
comprising an authentication token identifying the user of the documentation system;
querying, by the first backend instance, a database of the documentation system to obtain the secure page upon determining by the first backend instance that the user identified by the authentication token is authorized to access the secure page;
parsing, by the first backend instance, the secure page and identifying, by the first backend instance, a content tag designating a by-reference value within the secure page;
using the by-reference value, by the first backend instance to determine a project identifier corresponding to a project managed by the issue tracking system and a board identifier corresponding to a board associated with the project;
generating, by the first backend instance, an application programming interface (API) call to the issue tracking system, the API call formatted in accordance with an API schema determined using the by-reference value, the API call including the authentication token, the project identifier, and the board identifier;
providing the API call, by the first host server to a second host server executing a second backend instance providing backend functionality of the issue tracking system;
receiving, at the first backend instance from the second backend instance, a response including project timeline data associated with the board identifier and the project identifier, in response to the issue tracking system determining that the user identified by the authentication token is authorized to access the project identified by the project identifier and managed by the issue tracking system;
embedding, by the first backend instance, a timeline object including the project timeline data at a location corresponding to the content tag in the secure page of the documentation system; and
generating, by the first backend instance to the client application instance, a response comprising, from the documentation system, the secure page including the embedded timeline object that includes the project timeline data associated with the board identifier and the project identifier.