Skip to content
$ claude mcp add --transport http it4s https://mcp.it4s.at/mcp > search_issues project: SHOP status: open SHOP-87 Apple Pay payment fails ● In Progress > transition_issue SHOP-87 → in_review > create_issues parent: SHOP-80 (12 stories) ✓ SHOP-101 … SHOP-112 created > log_work SHOP-87 1h 30m "Apple Pay fix" ✓ logged · via Claude
BBuild agent · AI agentPR #212 opened · SHOP-87 → In Review
To Do
SHOP-91
OPS-14
APP-34
In Progress
SHOP-87
SHOP-83
In Review
APP-31
SHOP-80
Done
SHOP-60
APP-22
IT4S Issue Tracking
FeaturesAI & MCPPricingHelpAbout us
DeutschEnglish
Start free trial
FeaturesAI & MCPPricingHelpAbout usStart free trial
← User guide

Getting started

Getting startedTime zone of a workspaceTrial, limit warnings and inactive workspaces

Issues, board & releases

IssuesBoard, releases and documentationProject briefingTime tracking

AI agents & MCP

Working with AI agents and other appsAgents: personas for connected appsAI agents and your customers

Administration & billing

AdministrationRoles and customersPlan & BillingUpgrade to Team and billingArchive or delete a projectSilvertip support access

Moving over & integrations

Moving from Jira
Help › User guide › Time zone of a workspace

Time zone of a workspace

Updated: 2026-11-02

Every workspace works in its own time zone. Admins set it under Settings › General › Time Zone. New workspaces start with the zone chosen when they were created.

What follows the zone

  • What counts as today and overdue, and the days on My Work.
  • All dates and times shown in the workspace, for everyone in it, wherever they are.
  • The day a worklog counts for when you give a start time, and the times in the Worklogs view.
  • Reports, CSV and PDF exports, and dates in emails.
  • When a new day and a new month of API and MCP calls begin (Plan & Billing).
  • When the nightly backup runs: the first check after 2 at night in that zone.
  • Claude and other MCP clients: whoami tells them the zone; days they send, such as for log_work, are in it.

What doesn't move when you change the zone

  • Time already logged keeps its day. A worklog stays on the day it counted for when it was logged. Its start time is shown in the new zone, so near midnight the time can look as if it belongs to the neighbouring day.
  • Plain dates such as due dates and release dates stay the same date.

People in other zones see the workspace's times, not their own. That way "today" and reports mean the same for everyone in the workspace.

IT4S Issue Tracking

Pronounced “IT Force”. Issue tracking by Silvertip IT-Solutions from Innsbruck, Austria.

Product

FeaturesAI & MCPPricingCompared to Jira

Help

DocumentationFAQAPI referenceRelease notes

Company

About usContactLegal noticePrivacyTerms & DPACookiesSub-processors
© 2026 Silvertip IT-Solutions GmbH · Hosted in the EU