# Which of the caller's workspaces an issue key opens in, for an old link

For an old link that names an issue by key (`/tasks/issue/ENG-12`), so
the app can send the tab to `/tasks/w/<slug>/issue/<id>`. A key is
unique only within one workspace, so it can match in several of the
caller's workspaces: every match is listed (sorted by slug), and the
app offers a choice when there is more than one. It looks only in
workspaces the caller is a member of, at most 25.

A match is listed only when Tasks would let the caller open the issue
in its own workspace, by the same rules as `locateIssue`. When nothing
matches the answer is the same 404 as every other miss, never an empty
list: a malformed key, a request made with an API key or an OAuth
grant. Both answers are `Cache-Control: no-store`. Rate-limited per
user and per client IP, together with `locateIssue`.


Canonical: https://easerix.com/docs/developers/api/tasks/issues/locateIssueByKey

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

export default function Layout(props) {
  const { APIPage, OpenAPIPage } = props.components ?? {};
  // "APIPage" is the old name from v10, this allows both for backward compatibility
  const Comp = OpenAPIPage ?? APIPage;
  return (
    <>
      {props.children}
      <Comp document="tasks" operations={[{"path":"/v1/issues/locate","method":"get"}]} />
    </>
  );
}