Compare commits

..
86 Commits
Author SHA1 Message Date
github-actions[bot] 79cc436257 Bump versions for v13.22 2026-11-20 19:05:46 +00:00
Lauri Ojansivu 67fa4344c6 Prepare v13.22 release 2026-11-20 21:04:53 +02:00
Lauri Ojansivu 7b2d37fb41 Update WeKan changelog: Rocket.Chat and Fizzy.
Thanks to xet7 !
2026-11-20 20:29:28 +02:00
Lauri Ojansivu dffbafd30f Import and export Rocket.Chat and Fizzy.
Rocket.Chat: "Download my data" as JSON (channels.json and a message file
per room, with its assets), one room's .json, and the .zip Rocket.Chat's
CSV importer reads are imported for Board View / Chat - a room is a card,
its messages the comments. A board exports as that CSV importer .zip:
users.csv, channels.csv and a messages.csv per card.

Fizzy (37signals): its account export (data/<table>/<id>.json and
storage/) and personal data export (<number>.json per card) are imported -
boards become swimlanes, columns lists between Maybe?, Not now and Done,
with tags, assignees, steps, comments, golden and files. A board exports as
the account export Fizzy's account import reads, every row with every
column its import requires, ids as base36 UUIDv7.

Both formats are read and written from their projects' source code, with
tests, documentation and the import instruction in every language. Low
confidence translations include chr, ay, bm, bua, bo, cv, csb, ak, bi, ace,
ba, gn, gv, iu, kl, ig, kok, nah, qu, kw, lld, nap, rm, om, ks, tlh, tig,
rup, sah, se, ss, sm, to, tpi, dz, ee, ff, fj, fo, uz-AR, ve, ve-PP, vo,
wal, wa, wo, zgh, ve-CC, wa-RR, wuu-Hans, yi, xh and yo.

Thanks to xet7 !
2026-11-20 20:29:01 +02:00
Lauri Ojansivu dd57704ed1 Update WeKan changelog: Planner columns.
Thanks to xet7 !
2026-11-20 19:54:55 +02:00
Lauri Ojansivu d3aa34e7b8 Planner: the newer "Export as Excel" column names are read too; Linear is checked against its importer.
Microsoft's "Export a plan to Excel" page describes the newer Planner's
export with Status, Task title and Assignments, where the classic export
(the plannr fixture the tests use) writes Progress, Task Name and Assigned
To. The import now finds a column by either name, so the newer workbook is
not refused for a missing Task Name column. Linear's open-source importer
(@linear/import, LinearCsvImporter.ts) declares the columns the parser
reads, so Linear leaves TODO.md's list; Planner stays until a real newer
export confirms the exact header spelling.

tests/plannerFormat.test.cjs: the newer names, and a sheet without a title
column still refused.

Thanks to xet7 !
2026-11-20 19:54:54 +02:00
Lauri Ojansivu c5f30d8b7f Release audit: allow files.slack.com for the Slack file download.
The Slack import's file sign-in (models/lib/importAttachmentAuth.js) names
https://files.slack.com, the one host a Slack token is sent to, and the
release risk audit (tests/releaseTelemetry.test.cjs) stopped on the new URL
origin. It is added to that file's allowlist beside Asana's.

Thanks to xet7 !
2026-11-20 19:53:09 +02:00
Lauri Ojansivu 3a4163cfc3 TODO: Redmine and monday.com take a new column as a custom field; the proprietary tools are left.
Thanks to xet7 !
2026-11-20 19:44:54 +02:00
Lauri Ojansivu 2120be5ae1 Update WeKan changelog: GitLab health and severity.
Thanks to xet7 !
2026-11-20 19:44:34 +02:00
Lauri Ojansivu c916b15473 GitLab: an issue's health status and an incident's severity are kept as labels.
GitLab's Issues API v4 gives an issue a health_status (on_track,
needs_attention, at_risk) and an incident a severity, and the import
dropped both. They are now "health:..." and "severity:..." labels, as the
issue type is a "type:..." one; an UNKNOWN severity is none.

tests/gitlabImport.test.cjs: both labels, and none for a missing health or
an unknown severity.

Thanks to xet7 !
2026-11-20 19:44:33 +02:00
Lauri Ojansivu 0ef02911a8 TODO: GitHub checked against its REST issue; Focalboard's format is frozen since 2023.
Thanks to xet7 !
2026-11-20 19:43:51 +02:00
Lauri Ojansivu 246b23eaf7 Docs: GitHub's issue type as a type: label.
Thanks to xet7 !
2026-11-20 19:43:00 +02:00
Lauri Ojansivu b4e66b7584 Update WeKan changelog: GitHub issue types.
Thanks to xet7 !
2026-11-20 19:42:47 +02:00
Lauri Ojansivu 9ceb4dbf55 GitHub's issue type is kept as a "type:" label.
GitHub's issues have a type since 2025 (Bug, Feature, Task, or the
organization's own), { name, color, ... } on the issue, and the import
dropped it. It is now a "type:<name>" label, as the GitLab import keeps
issue_type.

tests/githubImport.test.cjs: the label, and none without a type.

Thanks to xet7 !
2026-11-20 19:42:46 +02:00
Lauri Ojansivu 49dd8dcb00 Update WeKan changelog: GitHub, Gitea and Forgejo dates and people.
Thanks to xet7 !
2026-11-20 19:42:20 +02:00
Lauri Ojansivu efeb55f57a GitHub, Gitea and Forgejo keep an issue's creation and close dates, people and Gitea's time estimate, both ways.
Checked against Gitea's current Issue struct (modules/structs/issue.go): the
import read neither created_at nor closed_at nor Gitea 1.23's
time_estimate, and the export wrote no dates, no assignee and no author, so
a round trip lost the creation date, the owner and the requester (as
tests/exportRoundTripFields.test.cjs showed). The import now reads
created_at as the creation date, closed_at of a closed issue as its end and
time_estimate (seconds) as the Time estimate (hours) custom field; the
export writes the owner as assignee and assignees, the creator as user,
created_at, closed_at of a closed issue and the time estimate.

tests/githubImport.test.cjs: the dates and the estimate, and an open issue
without an end; tests/exportRoundTripFields.test.cjs holds all three to the
creation date, owner and requester now.

Thanks to xet7 !
2026-11-20 19:42:18 +02:00
Lauri Ojansivu 85da7079fb TODO: Plane, Kanri, Obsidian Kanban and Nullboard checked against their current source; Pivotal Tracker is shut down.
Plane's current IssueExportSerializer has the fields the parser reads, in
the same order; Kanri's kanban-types.d.ts the board, column, card, task and
tag fields; Obsidian Kanban's parser the frontmatter key, settings block,
archive and complete markers; Nullboard's board object its format, id,
revision, title, lists and notes, and a history of revision numbers that
is not board data (noted in nullboardFormat.js). Pivotal Tracker was shut
down in 2025. They leave the list of tools still to check with a real
export.

Thanks to xet7 !
2026-11-20 19:40:31 +02:00
Lauri Ojansivu bb733d7692 Update WeKan changelog: Slack files.
Thanks to xet7 !
2026-11-20 19:38:17 +02:00
Lauri Ojansivu dd8242b82f Slack import downloads the messages' files with a Slack token.
A Slack export names each message file by its url_private on
files.slack.com, behind Slack's sign-in, and does not carry it; the import
counted every one. The import page's file sign-in now offers Slack too: with
a token of the files:read scope, each file is downloaded from
files.slack.com only - the token goes to no other host, and the download is
the import's guarded fetch like every other attachment - and attached to
the channel's card. Without a token a file is reported as not downloaded,
since Slack would answer with its sign-in page; a deleted file or one
hidden by the plan's history limit has no address and is counted.

tests/importAttachmentAuth.test.cjs: the token on Slack's file host only,
no download without one, the files on the channel card and the counted
ones.

Thanks to xet7 !
2026-11-20 19:38:16 +02:00
Lauri Ojansivu 709fa87f4a Update WeKan changelog: Super Productivity repeats.
Thanks to xet7 !
2026-11-20 19:35:50 +02:00
Lauri Ojansivu 35f3f6c9db Super Productivity export writes a repeating card's taskRepeatCfg, so it repeats there too.
The import read a task's repeat config, and the export wrote none, so a
repeating card came back from Super Productivity once. It was left until
the config could be checked against the app; it is now written with the
fields and defaults of Super Productivity's own model
(src/app/features/task-repeat-cfg/task-repeat-cfg.model.ts, TaskRepeatCfgCopy
and DEFAULT_TASK_REPEAT_CFG): every required field, the cycle and its quick
setting, the start date (due, or created), the weekday of a weekly repeat,
and today as the last creation day, since the card is this period's task.
An open card only, and the slice only when there is one.

tests/recurrenceMap.test.cjs: the required fields, the three cycles, no
config for a finished or one-off card, the task's repeatCfgId and the round
trip; tests/exportRoundTripFields.test.cjs: Super Productivity keeps the
recurrence.

Thanks to xet7 !
2026-11-20 19:35:49 +02:00
Lauri Ojansivu f918deef0f TODO: the import/export review is done against every documented format; what is left needs accounts on the tools or a running copy.
The review went through every parser and formatter; what it found is fixed
in the Upcoming release and held by the round-trip tests. The rest needs a
real export of each tool's newest release, a running Super Productivity, or
a Slack token, and is listed under the category that says so.

Thanks to xet7 !
2026-11-20 19:25:38 +02:00
Lauri Ojansivu deb4eed14e Update WeKan changelog: Telegram and Discord files.
Thanks to xet7 !
2026-11-20 19:25:18 +02:00
Lauri Ojansivu 828ca63713 Telegram and Discord imports bring their message files: a zipped export folder's photos and files are attachments.
Telegram Desktop writes result.json with photos/ and files/ beside it, and
DiscordChatExporter with --media a <name>.json_Files folder; the imports
read only the JSON and counted every file. Both now also take the export
folder zipped (the Import page, the many-files import and api.py): the
JSON is read as before, and every file its messages name by a local path
is read under the same per-file and whole-archive inflate limits as the
Slack zip (server/lib/chatArchives.js), then attached to the chat's card
through the generic importer's embedded-file path - so the after-upload
type and size checks of every upload apply. A file the folder does not
carry ("File not included", a Discord link) is still counted; a file no
message names is not read.

tests/chatExportFormats.test.cjs: both zips, only the named files read, the
left-out file counted, the JSON alone as before, and the wiring.
tests/importSources.test.cjs: the zip sources, and api.py agreeing.

Thanks to xet7 !
2026-11-20 19:25:17 +02:00
Lauri Ojansivu 133be01324 Update WeKan changelog: Linear cycles.
Thanks to xet7 !
2026-11-20 19:20:45 +02:00
Lauri Ojansivu 75694ac644 Linear cycles become Scrum sprints and project milestones Scrum releases.
Linear's CSV export carries each issue's cycle with its Cycle Start and
Cycle End, and its project milestone, and the import kept the cycle name as
a custom field and reported the dates and the milestone. With Scrum ticked
in the import, each cycle is now a sprint with those dates - one per team,
since a cycle number is its team's - and each project milestone a release,
through models/lib/externalScrumPlanning.js like GitLab's iterations and
Pivotal's. As for Pivotal and Jira, a cycle whose issues are all done is
finished and not imported (no commitment or close snapshot in the export),
and any other is planned; a milestone has no dates in the CSV. Both are in
the loss report.

tests/linearCsv.test.cjs pinned the cycle dates and milestones as lost
columns and now pins the sprints and releases, per team, with the finished
cycle and an issue without either.

Thanks to xet7 !
2026-11-20 19:20:44 +02:00
Lauri Ojansivu 9a18cc3dda Update WeKan changelog: Basecamp steps.
Thanks to xet7 !
2026-11-20 19:17:27 +02:00
Lauri Ojansivu a72b297268 Basecamp card steps keep their due date and assignee.
A Basecamp card step has its own due_on and assignees, and the import kept
only its title and done mark; a WeKan checklist item has a due date and an
assignee too (models/lib/importedTaskPlan.js importedChecklists). The step's
due date and first assignee are now its item's.

tests/basecampApiImport.test.cjs: the step's fields onto the checklist
item, and a step without them.

Thanks to xet7 !
2026-11-20 19:17:26 +02:00
Lauri Ojansivu 651378d163 Update WeKan changelog: Taiga blocked.
Thanks to xet7 !
2026-11-20 19:15:35 +02:00
Lauri Ojansivu ab884547f4 Taiga's blocked state is the card's Blocked flow field, both ways.
WeKan cards have a Blocked flow field with a reason, and the Taiga import
put is_blocked / blocked_note into a "Blocked" custom field, from before the
flow field existed. A normalized task may now carry blocked and
blocked_reason, which the shared import plan writes as the card's flow
field; the importer turns on Board Settings / Card's Blocked display for a
board with a blocked card, since flow fields are off until a board shows
them. Taiga uses it, and its export writes the card's Blocked flow field
(or the custom field of a board imported before) back to is_blocked and
blocked_note.

tests/taigaFormat.test.cjs pinned the custom field and now pins the flow
field, the board display and the export; tests/exportRoundTripFields.test.cjs
holds every format to whether it keeps Blocked.

Thanks to xet7 !
2026-11-20 19:15:34 +02:00
Lauri Ojansivu 8ac7afe95f Update WeKan changelog: Todoist and TickTick columns.
Thanks to xet7 !
2026-11-20 19:04:21 +02:00
Lauri Ojansivu c72a05d11a Todoist and TickTick report a column they do not write, instead of dropping it.
A sweep of the CSV imports with an extra column (each format's own export
plus one) found Linear, MeisterTask, Pivotal and Quire reporting it,
Redmine, Notion and now ClickUp keeping it as a custom field - and Todoist
and TickTick dropping it without a word. Their own exports have fixed
columns, so an extra one is a hand-edited file; it is now named in the loss
report.

tests/todoistCsv.test.cjs and tests/ticktickCsv.test.cjs: the report, and
none for the format's own export.

Thanks to xet7 !
2026-11-20 19:04:20 +02:00
Lauri Ojansivu 01f52748f3 Update WeKan changelog: ClickUp custom fields.
Thanks to xet7 !
2026-11-20 19:03:04 +02:00
Lauri Ojansivu 60f569afe6 ClickUp: a workspace's custom field columns come across both ways, and the task link is kept.
A ClickUp workspace export writes each custom field as a column of its own,
and the import dropped every column it did not name - Story Points, Sprint,
any field of the workspace's - without a word, as it dropped Task Link.
Every column ClickUp does not name is now a custom field of its name, the
export writes a card's other custom fields back as columns (named over the
whole board, so every page has the same header), and the Task Link is
"Source: <link>" at the end of the description, as other imports keep a
source's link. ClickUp's own Rolled Up Time and Text columns repeat other
columns and are still not read.

tests/clickupCsv.test.cjs: both ways, one column per field, ClickUp's own
columns not made fields, and the Source line.

Thanks to xet7 !
2026-11-20 19:03:03 +02:00
Lauri Ojansivu d8fff9a41a Update WeKan changelog: Notion relations.
Thanks to xet7 !
2026-11-20 19:01:15 +02:00
Lauri Ojansivu f546ff2383 Notion relations between rows of an export become "related to" dependencies.
A Notion relation column names the related pages by title and path, and
the import reported every relation column as not imported. A related page
that is exactly one row of the export, in any of its databases, is now a
"related to" dependency between the two cards. A relation to a page that is
not a row, or to a title two rows share, is not guessed and is counted in
the loss report.

tests/notionFormat.test.cjs pinned the relation column as a loss and now
pins the dependency, with the negative cases.

Thanks to xet7 !
2026-11-20 19:01:13 +02:00
Lauri Ojansivu e38168789d Update WeKan changelog: Push Snap to Store.
Thanks to xet7 !
2026-11-20 18:59:04 +02:00
Lauri Ojansivu ce646dc937 Push Snap to Store releases what the store already has, each channel on its own, and uploads a file once.
The v13.20 and v13.21 runs uploaded wekan_13.21_amd64.snap again and again,
each time answered "Error checking upload uniqueness", and never released
it. The cause: snapcraft 9 renamed list-revisions to revisions, and the old
name only prints that and fails, so the script never found the revision the
store already had, and the store takes a file only once. On the dashboard
the wekan and wekan-gantt-gpl 13.21 revisions are "Can't be released:
ReviewQueued" - held for the store's manual review, greyed out on the web
too.

Now:
- the store's revisions are read with `snapcraft revisions` (the old name
  for an older snapcraft), and a revision the store has is released, never
  uploaded again;
- a file is uploaded once by default; after "Error checking upload
  uniqueness" the store's revision is released, or reported as held with
  how to ask for the review;
- every release goes to each channel on its own, so one the store refuses
  does not keep the revision out of the others, and each refusal is an
  error line in the log;
- after a release's files, the newest revision of every architecture the
  store has is released to every channel too
  (releases/snap-store-release-newest.sh), whatever the GitHub release
  holds - a revision approved later is released by the next run;
- a release with no wekan-ondra or wekan-gantt-gpl snap gets them made from
  its wekan snaps (releases/snap-rename.sh), as Release All Missing does;
- the release-time upload (snap-upload-retry.sh) still retries a
  uniqueness error (on v10.78 a store glitch), and when it outlasts the
  retries reports the file as held instead of failing the build.

Release All and Release All Missing both end by calling this workflow, so
the same steps run in all three. tests/snapStorePush.test.cjs and
tests/snapUploadProcessingBudget.test.cjs drive the scripts with a fake
snapcraft that answers as snapcraft 9 does.

Thanks to xet7 !
2026-11-20 18:59:03 +02:00
Lauri Ojansivu ae1f084fb1 Update WeKan changelog: subtask due dates and people.
Thanks to xet7 !
2026-11-20 18:37:54 +02:00
Lauri Ojansivu cf6f67e789 Imported subtasks keep their due date and person: a checklist item has both.
A WeKan checklist item has a due date and an assignee, and the shared
import plan and writer carried only its title and done mark - so Google
Tasks and KanbanFlow reported a subtask's due date and person as having "no
place on a WeKan checklist item". A normalized item may now carry `due` and
`assignee`; the plan maps the person to a board member (left out when not
mapped) and the writer stores dueAt and assigneeId. Google Tasks keeps a
subtask's due date, KanbanFlow its due date and person; a subtask's notes
and links are still reported.

tests/kanbanflowApiImport.test.cjs pinned the loss and now pins the item's
due date and assignee; tests/googletasksApiImport.test.cjs: the due date,
the notes still reported, and a due date that is no date.

Thanks to xet7 !
2026-11-20 18:37:53 +02:00
Lauri Ojansivu 3ccce83480 Update WeKan changelog: Planka 2.
Thanks to xet7 !
2026-11-20 18:29:00 +02:00
Lauri Ojansivu 0d65eec4f2 Planka 2: custom fields and stopwatch time come across.
Planka 2's custom fields (customFieldGroups, customFields,
customFieldValues) and a card's stopwatch were reported as not imported,
though imports make custom fields and WeKan cards have spent time. A value
is now the card's custom field of its field's name - "Group: Field" when two
groups have a field of that name - and the stopwatch total (seconds) is the
spent time. A value of a field the export does not name is still reported.

tests/plankaApiImport.test.cjs: both, the group disambiguation, and the
unnamed field.

Thanks to xet7 !
2026-11-20 18:28:58 +02:00
Lauri Ojansivu b26b148779 Update WeKan changelog: Asana.
Thanks to xet7 !
2026-11-20 18:27:33 +02:00
Lauri Ojansivu 57a657445e Asana: html_notes, approval states and comment likes come across.
An Asana API export asked for html_notes may carry only those, and the
card came in without a description; an approval task's approved, rejected
or changes-requested state, and who liked a comment, were dropped without a
word. The rich text is now the description, as text (the Microsoft To Do
body's careful stripping), the approval state a label, and a comment
story's likes its 👍 reactions, by who liked it - the likes the export does
not name are counted in the loss report.

tests/asanaImport.test.cjs: each of them, notes winning over html_notes,
and a pending approval being no state.

Thanks to xet7 !
2026-11-20 18:27:32 +02:00
Lauri Ojansivu b5a97bcd11 Update WeKan changelog: templates.
Thanks to xet7 !
2026-11-20 18:26:16 +02:00
Lauri Ojansivu a4359731b1 WeKan import keeps templates: a template board, card, list or swimlane stays a template.
The WeKan JSON import wrote no board, card, list or swimlane type, so a
template board came back as an ordinary board and its card, list and
swimlane templates as ordinary ones. tests/wekanCardFields.test.cjs did not
catch it: "type" appears elsewhere in wekanCreator.js (attachments have one)
and counted as written.

Now template-board, template-card, template-list and template-swimlane are
kept. A user's own Templates board (template-container) is imported as a
template board, since the importing user's Templates board is the one their
profile points to, and the loss report says so; its section swimlanes
become ordinary swimlanes. A linked card or board points at the exporting
WeKan, so it comes as an ordinary card.

Attachment versions need nothing: the original is the file, and a thumbnail
is made from it when first shown (#3275). A part of a board is exported by
Board Settings / Export's scope and imports as a board of its own. Both are
noted in the docs, and the WeKan item leaves TODO.md.

Thanks to xet7 !
2026-11-20 18:26:15 +02:00
Lauri Ojansivu c05ff7b9a8 TODO: the plain-Node round-trip test covers 32 formats.
Thanks to xet7 !
2026-11-20 18:24:09 +02:00
Lauri Ojansivu d7b0641295 Changelog: shorten the export round-trip summary.
Thanks to xet7 !
2026-11-20 18:24:02 +02:00
Lauri Ojansivu 105a1ed0c1 Update WeKan changelog: export round-trip fields.
Thanks to xet7 !
2026-11-20 18:23:48 +02:00
Lauri Ojansivu 1a02de4b5b Every export is held to what its own import reads back: Asana time tracking, Deck's done tick, Kanboard colors.
tests/exportRoundTripFields.test.cjs exports a card with every field set in
each of the 32 formats WeKan both writes and reads as text or JSON, parses
the file back, and holds each format to a KEEPS table of start and creation
dates, spent time, the due date's done tick, recurrence, owner, requester,
custom fields and color - the fields the Playwright round-trip spec does not
look at. A format that keeps less, or more, fails until its line changes.

What it found, fixed here:
- Asana: the import did not read actual_time_minutes, Asana's time
  tracking, and the export did not write it. Both do now.
- Nextcloud Deck: the export wrote done only with an end date, so a due date
  ticked done came back not done. It writes done: true then, which the
  import reads.
- Kanboard: the import mapped color_id to a card color and the export wrote
  none. It writes it back (the map moved to models/lib/kanboardFields.js).
(Kanboard, OpenProject, ClickUp and GitLab were fixed in the commits before.)

Thanks to xet7 !
2026-11-20 18:23:47 +02:00
Lauri Ojansivu 59ee94667d Update WeKan changelog: ClickUp and GitLab spent time.
Thanks to xet7 !
2026-11-20 18:14:11 +02:00
Lauri Ojansivu 14afc74adb ClickUp and GitLab exports write spent time, which their imports read and a round trip lost.
Both imports read a task's spent time (ClickUp's Time Spent milliseconds,
GitLab's time_stats.total_time_spent seconds), and neither export wrote it.
They do now, in the same units, so it comes back.

tests/clickupCsv.test.cjs and tests/gitlabImport.test.cjs: the round trip,
and nothing written when nothing was spent.

Thanks to xet7 !
2026-11-20 18:14:10 +02:00
Lauri Ojansivu ab1067e0b1 Update WeKan changelog: OpenProject time.
Thanks to xet7 !
2026-11-20 18:12:49 +02:00
Lauri Ojansivu 9bd503a71b OpenProject: remaining time is imported, and spent time is exported, so it survives a round trip.
The import read a work package's spentTime and estimatedTime but not its
remainingTime, and the export wrote no spentTime at all, so a card's spent
hours were lost on the way out. remainingTime is now the custom field
Remaining time (hours), and the export writes the spent hours as an ISO 8601
spentTime (PT1.5H), which the import reads back.

tests/openProjectImport.test.cjs: both ways, and none written when there is
none.

Thanks to xet7 !
2026-11-20 18:12:48 +02:00
Lauri Ojansivu a81050e9b8 Update WeKan changelog: Deck label colors.
Thanks to xet7 !
2026-11-20 18:11:33 +02:00
Lauri Ojansivu 22d000b913 Nextcloud Deck labels keep their colors.
A Deck label has a hex color, and the import created every label black.
The label now carries its color to the board label (hex colors are label
colors since #5514; models/lib/importedTaskPlan.js planImportedLabels
already took them from Kanri). A label without one stays black.

tests/deckImport.test.cjs pinned the bare label name and now pins the
color, onto the board label, with the colorless case.

Thanks to xet7 !
2026-11-20 18:11:32 +02:00
Lauri Ojansivu 1081ea7c88 Update WeKan changelog: Kanboard recurrence and fields.
Thanks to xet7 !
2026-11-20 18:10:05 +02:00
Lauri Ojansivu 28891103f6 Kanboard keeps its task recurrence, estimate, score, reference and external links, both ways.
WeKan's card recurrence was modelled on Kanboard's, and the Kanboard import
ignored a task's recurrence_status / _factor / _timeframe; it reported the
estimate as having no place although imports make custom fields; it
reported external links, and dropped score and reference without a word.
Now a repeat every 1 day, 7 days or 1 month is the card's recurrence (any
other is reported), time_estimated, score and reference are custom fields,
and each external link is a line of the description. The export writes
time_spent, the recurrence of an open card and those custom fields back.
The shared helpers are models/lib/kanboardFields.js, so the formatters,
which load on the client too, do not pull in the parsers.

tests/kanboardImport.test.cjs: both ways and the negative cases; it pinned
the estimate as a loss and now pins the custom field.
tests/recurrenceMap.test.cjs accepts a recurrence read through a module that
uses the mapper.

Thanks to xet7 !
2026-11-20 18:10:04 +02:00
Lauri Ojansivu a86e9d34e8 TODO: issue tracker reactions are reported; the rest is checked against each tool's export docs.
Thanks to xet7 !
2026-11-20 18:00:08 +02:00
Lauri Ojansivu 57413fd66a Update WeKan changelog: issue reaction counts.
Thanks to xet7 !
2026-11-20 17:59:59 +02:00
Lauri Ojansivu 1b9ec7b9a1 GitHub, Gitea, Forgejo and GitLab imports report reaction counts instead of dropping them.
An issue's and its comments' reactions summary (GitHub, Gitea, Forgejo) and
GitLab's upvotes and downvotes are counts, without who reacted. A WeKan
reaction is kept by who reacted (models/lib/importedReactions.js), so they
cannot come across - but they were dropped without a word. The loss report
now counts them.

tests/githubImport.test.cjs: the counts reported, and none when there are
none.

Thanks to xet7 !
2026-11-20 17:59:58 +02:00
Lauri Ojansivu 2268f9d8bd Update WeKan changelog: WeKan import keeps lists, checklists, custom fields and replies.
Thanks to xet7 !
2026-11-20 17:58:38 +02:00
Lauri Ojansivu 24b6b9b024 WeKan JSON import keeps lists' WIP limits, policies and splits, checklist settings, custom field access, item assignees and comment replies.
The same gap as the board and its cards, one level down: a list came back
without its WIP limit, flow policy, split into Doing and Done and role
restrictions; a swimlane without its height; a checklist without its hide
settings and reset schedule; an item without its assignee; a custom field
without "admin only" and "read only" - so a field only admins could see or
edit was open to everyone on the imported board; a reply without the
comment it answers.

models/lib/wekanRecordFields.js writes them, with the users, cards and
comments they name remapped (left out when they did not come), a
checklist's reset counted from the import, and a reply linked even when its
comment comes later in the export. A list role exception is kept only where
it restricts a role: a file does not open a list to a role the board's rule
keeps out. Sync bookkeeping, trash state and other boards' ids are named
with the reason they are not written.

tests/wekanCardFields.test.cjs holds every list to its schema, with
negative tests. The Meteor mocha tests of wekanCreator were not run here.

Thanks to xet7 !
2026-11-20 17:58:37 +02:00
Lauri Ojansivu 07f1028d03 Update WeKan changelog: WeKan import keeps every board and card field.
Thanks to xet7 !
2026-11-20 17:49:20 +02:00
Lauri Ojansivu c640c5c376 WeKan JSON import keeps every board and card field: all Board Settings, flow fields, votes, poker, stickers, drawings.
The WeKan JSON export writes the whole board and card documents, and the
import wrote 32 of the 210 board fields and about 30 of the 87 card fields.
A board exported and imported back came back with every Board Settings
choice at its default - what a card and a minicard show and in which order,
the flow policies, the board views, column sets, WIP limit groups, the date
format, notification delivery, the announcement - and its cards without
their flow fields (Blocked, Class of service, MoSCoW, WSJF), votes, planning
poker, stickers, locations, drawings, column-set columns, the due date's
done tick, mail headers, kind, map position and display settings.

models/lib/wekanBoardFields.js and wekanCardFields.js now write them, with
the users in a vote, a poker card or "blocked by" mapped to the new board's
(left out when they are not on it), lists remapped in the commitment point
and WIP limit groups, and a drawing's PNG by its new attachment id. The
Board Settings are written once the lists exist; a value the schema refuses
- from an older or newer WeKan - is left at its default and reported, and
the WeKan import now has a loss report at all. Not written, each with its
reason: access (organizations, teams, domains, instance editing) and
inbound email, which a file must not turn on; the trash, sync bookkeeping
and running timers; ids of other boards.

tests/wekanCardFields.test.cjs holds both lists to the schemas, so a field
added to WeKan is imported or named with why it is not. The Meteor mocha
tests of wekanCreator were not run here.

Thanks to xet7 !
2026-11-20 17:49:19 +02:00
Lauri Ojansivu 0999864cef Update WeKan changelog: chat threads.
Thanks to xet7 !
2026-11-20 17:35:52 +02:00
Lauri Ojansivu 1122e49ca9 Chat imports keep threads: a reply is a reply to the comment of the message it answers.
Slack (thread_ts), Mattermost (nested replies), Telegram
(reply_to_message_id) and Discord (reference) all say which message a reply
answers, and WeKan comments have replies (parentId, one level deep) - but
the import made every reply a comment of its own, a "↳" line at best. The
parsers now give each message its id and the id it answers, the import plan
(threadImportedComments) turns that into the comment it goes under -
flattened to one level, as WeKan's replies are - and the writer stores its
parentId. A reply to a message that is not in the file stays a comment of
its own, marked "↳".

tests/importedThreads.test.cjs: the four exports through the plan, the
writer, and the negative cases. tests/chatExportFormats.test.cjs pinned the
"↳" text and now pins the thread link.

Thanks to xet7 !
2026-11-20 17:35:51 +02:00
Lauri Ojansivu f72277a398 Update WeKan changelog: chat reactions.
Thanks to xet7 !
2026-11-20 17:33:47 +02:00
Lauri Ojansivu f467e31d17 Chat imports keep reactions: Slack, Mattermost, Telegram and Discord reactions become the comments' reactions.
All four exports say who reacted to a message with what, and WeKan
comments have reactions (card_comment_reactions: an emoji code point and the
users who reacted) - but every reaction was dropped without a word in the
import loss report. models/lib/importedReactions.js turns an emoji, or a
Slack / Mattermost shortcode, into the code point WeKan stores, and keeps a
reaction for each person mapped to a WeKan user. The import plan carries
them, the inserter writes the comment's reaction row, and the loss report
counts the reactions of people not mapped and those WeKan cannot store: an
unknown shortcode, a server's own emoji, several code points (a skin tone,
a flag).

tests/importedReactions.test.cjs: the mapping, the four parsers, the plan,
the writer, and negative tests - including that nothing else builds a
reaction code point.

Thanks to xet7 !
2026-11-20 17:33:46 +02:00
Lauri Ojansivu 8ff76652d4 TODO: the task tools keep priorities, sub-tasks, sections and repeats; the Super Productivity repeat export is left.
Thanks to xet7 !
2026-11-20 17:21:44 +02:00
Lauri Ojansivu 20c4d90217 Update WeKan changelog: Markdown labels, due dates and checklists.
Thanks to xet7 !
2026-11-20 17:21:08 +02:00
Lauri Ojansivu 10caa20b09 Markdown: #tags, due dates and indented checkboxes are labels, due dates and checklists, both ways.
The Markdown import read only a card's title, done mark and indented text:
the #tags and due dates markdown-kanban tools write stayed in the title, and
an indented "- [ ]" line - the card's checklist in those tools - became
description text. The export wrote neither labels, dates nor checklists.

Now #tag words are labels (a word starting with a letter: not "#1234", not
"C#"), @{day} @@{time} (Obsidian Kanban), 📅 day (Obsidian Tasks) and
due:day (todo.txt) are the due date, and indented checkboxes are the
checklist. The export writes them back, escaping a description line that
looks like a checklist item as "\- [ ]" so it reads back as text. A due day
that is no date is reported.

tests/markdownImportExport.test.cjs: both ways and the negative cases. The
round-trip spec's KEEPS table now has Markdown keep the checklist, label
and due date; that Playwright spec was not run here.

Thanks to xet7 !
2026-11-20 17:21:07 +02:00
Lauri Ojansivu 720374efd8 Update WeKan changelog: Leo creation dates.
Thanks to xet7 !
2026-11-20 17:18:52 +02:00
Lauri Ojansivu 3be07b147b Leo: a node's id stamp is the card's creation date, both ways; plugin data is reported.
Leo stamps every node's id (gnx) with the time it was made -
ekr.20260902080910.2 - and the import read it only as a key, while the
export wrote ids as wekan.1.N: a card's creation date was lost both ways.
The import now takes the time from the gnx (local time, read as UTC, as Org
does), and the export writes wekan.YYYYMMDDHHMMSS.n for a card that has a
creation date. Attributes of a <v> or <t> that Leo itself does not write are
its plugins' pickled data, dropped without a word until now; they are
reported.

tests/leoOutline.test.cjs: both ways, invalid stamps, and Leo's own
attributes not reported. tests/exportPaging.test.cjs looked a card's gnx up
as wekan.1.N and now accepts the stamped form.

Thanks to xet7 !
2026-11-20 17:18:50 +02:00
Lauri Ojansivu c2a9c36829 Update WeKan changelog: OPML attributes.
Thanks to xet7 !
2026-11-20 17:16:48 +02:00
Lauri Ojansivu 95b88095c4 OPML keeps created, category, links and an outliner's own attributes.
A card outline's created (OPML 2.0's creation date), its category (its
tags), and any attribute of the outliner's own - OmniOutliner writes its
columns as attributes - were dropped without a word, and a url / htmlUrl /
xmlUrl link was only reported. Now created is the creation date, each
comma-separated category a label (its leading "/" taken off), a link goes at
the end of the description, and any other attribute is a custom field. The
export writes created (RFC 822) and the labels as category. An attribute of
a list or a checklist item, and a created that is not a date, are reported;
type, isComment and isBreakpoint only say how a row is drawn.

tests/opmlOutline.test.cjs: both ways and the negative cases. The
round-trip spec's KEEPS table now has OPML keep labels; that Playwright
spec was not run here.

Thanks to xet7 !
2026-11-20 17:16:47 +02:00
Lauri Ojansivu 18740f4c22 Update WeKan changelog: every CSV, TSV and Excel column.
Thanks to xet7 !
2026-11-20 17:14:58 +02:00
Lauri Ojansivu 5b9fa791a8 CSV, TSV and Excel imports keep every column: one with no card field becomes a text custom field.
A column the header guess had no field for - "Story points", "Sprint", any
column of the user's own - was imported only when ticked in the import
page's mapping step, and dropped without a word otherwise: always for a REST
import, which sends no mapping, and on the page unless someone ticked it.
guessCsvMapping now puts every other named column in customFieldColumns,
and the mapping step starts with them ticked, so nothing is left behind
unless it is unticked. WeKan's own Number, Last activity and Voting columns,
a blank header and a number cell of a sparse row (#6620) are not made fields.

tests/csvCreator.headerMapping.test.cjs pinned "unknown headers are not
mapped" and now pins that the column comes across, with the negative cases.

Thanks to xet7 !
2026-11-20 17:14:37 +02:00
Lauri Ojansivu b1ab04a764 Update WeKan changelog: Org mode properties and clocks.
Thanks to xet7 !
2026-11-20 17:12:47 +02:00
Lauri Ojansivu 55c3f574f4 Org mode: every property is kept, :ID: is the card's reference, LOGBOOK clocks are its spent time.
Of an Org heading's property drawer only :CREATED: was read, and the rest
of it - :ID:, :EFFORT:, any property of the user's own - and the whole
:LOGBOOK: drawer were dropped without a word in the import loss report.
Now :ID: / :CUSTOM_ID: is the card's source reference, every other property
is a custom field of that name (:NAME+: appends), and the closed CLOCK
lines add up to the spent time. The export writes the custom fields back as
properties. An open clock, a property line that is not :NAME: value, a
:CREATED: that is not a date and any other drawer are reported.

tests/orgMode.test.cjs: the round trip and the negative cases.

Thanks to xet7 !
2026-11-20 17:12:38 +02:00
Lauri Ojansivu 1984f72d5e Update WeKan changelog: Tasks.org, Vikunja and Super Productivity repeats.
Thanks to xet7 !
2026-11-20 17:10:39 +02:00
Lauri Ojansivu 878e53f418 Tasks.org, Vikunja and Super Productivity repeats become the card's recurrence too.
The rest of the task tools with a repeat rule, through
models/lib/recurrenceMap.js like the others:
- Tasks.org: the task's RRULE, imported and written back.
- Vikunja: repeat_after of a day or a week, repeat_mode 1 (monthly),
  imported and written back.
- Super Productivity: a task's repeatCfgId points to a taskRepeatCfg; one
  repeating every 1 day, week or month, not paused, makes the card repeat.
  Writing a repeat config back on export is left in TODO.md: it needs the
  app's scheduler fields checked against a running Super Productivity.
Any other rule, and the repeat of a finished task, stays in the import loss
report. Google Tasks' API has no repeat to read.

tests/recurrenceMap.test.cjs covers all three with negative tests; the
Tasks.org and Vikunja suites pinned "imported once" and now pin the repeat.

Thanks to xet7 !
2026-11-20 17:10:18 +02:00
Lauri Ojansivu 887fdc7e6d Merge remote-tracking branch 'origin/main' 2026-11-20 17:01:56 +02:00
Lauri Ojansivu bfdb37526e Update WeKan changelog: repeating tasks, snaps on every Snap Store channel.
Thanks to xet7 !
2026-11-20 16:59:46 +02:00
Lauri Ojansivu dc0a1ad049 Snaps: Release All pushes wekan, wekan-ondra and wekan-gantt-gpl to every Snap Store channel; Release All Missing adds what a release lacks.
The Push Snap to Store run for v13.20 failed three ways:
- wekan-ondra and wekan-gantt-gpl: "no assets match the file pattern". The
  snap-variants job uploaded them to the store but never attached them to
  the GitHub Release. It does now (github-release-upload.sh, on always()
  after its verify step).
- wekan: the store answered "Error checking upload uniqueness", a store-side
  failure, and snap-store-push.sh then waited two hours for a revision that
  upload never made. It now uploads again after a store failure (5xx,
  uniqueness), waits only when the store is really processing or already has
  the file, and fails at once on any other refusal.
- It ran on workflow_run and took "the latest release", which was v13.20.
  Release All now ends with a snap-store job that calls the workflow
  (workflow_call) for the tag it released, after snap-native,
  snap-launchpad and snap-variants.

Release All Missing:
- expected-assets.sh lists the snaps: wekan on six architectures, the two
  variants on amd64 and arm64.
- A missing variant snap is made from the release's own wekan snap by
  releases/snap-rename.sh, which changes only name and title in
  meta/snap.yaml - what snap-variants changes - and attached; then the
  release's snaps are pushed to the store.
- With no version, a scan job (releases/release-missing-scan.sh) checks the
  newest releases and starts one run per release missing something.
- What it cannot build no longer fails the plan, which skipped every build
  that could have been made; the done job is red for it at the end.

tests/snapStorePush.test.cjs: the retry and the immediate refusal, both
workflows, the rename and the scan, with fake snapcraft, squashfs and gh.

Thanks to xet7 !
2026-11-20 16:59:23 +02:00
Lauri Ojansivu 24ac6b2bd2 Repeating tasks of other tools repeat in WeKan: daily, weekly and monthly as the card's recurrence.
WeKan cards can repeat daily, weekly or monthly, but no import set it and no
export wrote it: Taskwarrior, Microsoft To Do, Todoist, TickTick, iCalendar,
Org mode and Obsidian Kanban all reported a repeat as lost and imported the
task once. models/lib/recurrenceMap.js reads their rules - RRULE, recur,
Org repeaters, "every week", To Do patterns - and returns daily, weekly or
monthly only when the rule is exactly that; anything else (every two weeks,
yearly, weekdays, a count or an end) stays in the import loss report.

The import plan sets recurrenceInterval and lastRecurrenceAt = the import
time, so the recurrence job does not copy every imported card at once from
its old creation date. Of Taskwarrior's instances, only the newest open one
of each template repeats. A finished task's repeat is reported, not kept.
The exports write it back: Taskwarrior recur, Org +1w, Obsidian 🔁, TickTick
Repeat, and RRULE in the iCal feed. The WeKan JSON import now keeps
recurrenceInterval too.

tests/recurrenceMap.test.cjs: every format both ways, and negative tests -
rules WeKan cannot keep stay reported, and no import sets a recurrence
outside the three or without the mapper. The five format suites that pinned
"imported once" now pin the repeat.

Thanks to xet7 !
2026-11-20 16:59:14 +02:00
405 changed files with 7103 additions and 1221 deletions

No files matched your search

+134 -6
View File
@@ -53,9 +53,14 @@ on:
workflow_dispatch:
inputs:
version:
description: 'Release to complete, without the v (e.g. 10.58). Empty = the newest release.'
description: 'Release to complete, without the v (e.g. 10.58). Empty = check the newest releases and complete each one that is missing something.'
required: false
type: string
scan:
description: 'With no version: how many of the newest releases to check.'
required: false
type: string
default: '10'
# Read-only by default; the job that writes is granted it below.
permissions:
@@ -74,6 +79,10 @@ concurrency:
jobs:
recover:
# One release at a time: with no version, scan below starts a run of this
# workflow for every release that is missing something, and each of those
# recovers its own release.
if: ${{ inputs.version != '' }}
permissions:
contents: read
actions: write
@@ -95,6 +104,41 @@ jobs:
[ -n "$V" ] || V="$(gh release view --repo "$GITHUB_REPOSITORY" --json tagName --jq .tagName)"
python3 releases/retry-failed-release.py "$V"
# With no version: which releases are missing something. Each of them gets a
# run of its own (`-f version=...`), which does everything below for it -
# retries the failed jobs of its full release, builds what can be built,
# renames the variant snaps and finishes its Snap Store release - so one
# run of this workflow, with no input, adds everything that is missing.
scan:
if: ${{ inputs.version == '' }}
permissions:
contents: read
actions: write
timeout-minutes: 15
name: which releases are missing something
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Start a run for each incomplete release
env:
GH_TOKEN: ${{ github.token }}
SCAN: ${{ inputs.scan }}
run: |
set -euo pipefail
case "${SCAN:-10}" in ''|*[!0-9]*) echo "::error::scan must be a number of releases, not '$SCAN'."; exit 1 ;; esac
bash releases/release-missing-scan.sh "${GITHUB_REPOSITORY:-wekan/wekan}" "${SCAN:-10}" > incomplete.txt
{
echo "### Releases missing something"
echo ""
if [ -s incomplete.txt ]; then sed 's/^/- /' incomplete.txt; else echo "None - the ${SCAN:-10} newest releases are complete."; fi
} >> "$GITHUB_STEP_SUMMARY"
while read -r version count; do
echo "v$version is missing $count asset(s): starting Release all missing for it."
gh workflow run release-all-missing.yml --repo "${GITHUB_REPOSITORY:-wekan/wekan}" --ref "${GITHUB_REF_NAME:-main}" -f version="$version"
done < incomplete.txt
plan:
needs: recover
# The planner runs whatever recover's rerun ended with. A rerun that still
@@ -102,7 +146,7 @@ jobs:
# so in every rerun of it (v12.68's OpenBSD start) - used to skip the
# planner and every build after it, so not even the assets that COULD be
# filled were. recover stays red and names the jobs; the rest goes on.
if: ${{ !cancelled() }}
if: ${{ !cancelled() && inputs.version != '' }}
timeout-minutes: 15
name: what the release is missing
runs-on: ubuntu-latest
@@ -114,6 +158,8 @@ jobs:
mac: ${{ steps.plan.outputs.mac }}
flatpak: ${{ steps.plan.outputs.flatpak }}
windows: ${{ steps.plan.outputs.windows }}
variant: ${{ steps.plan.outputs.variant }}
snap: ${{ steps.plan.outputs.snap }}
manual: ${{ steps.plan.outputs.manual }}
total: ${{ steps.plan.outputs.total }}
steps:
@@ -168,7 +214,7 @@ jobs:
total="$(wc -l < missing.txt | tr -d ' ')"
echo "total=$total" >> "$GITHUB_OUTPUT"
for kind in extra appimage mac flatpak windows bun; do
for kind in extra appimage mac flatpak windows bun variant snap; do
sels="$(awk -v k="$kind" '$1 == k { print $2 }' missing.txt)"
json="$(printf '%s\n' $sels | sed '/^$/d' | jq -R . | jq -sc .)"
[ -n "$json" ] || json='[]'
@@ -197,18 +243,25 @@ jobs:
echo ""
echo "Not buildable here (run release-all.yml): \`$manual\`"
fi
if grep -q '^snap ' missing.txt; then
echo ""
echo "wekan snaps are rebuilt by retrying the release's snap-native or snap-launchpad job (recover, above)."
fi
fi
} >> "$GITHUB_STEP_SUMMARY"
echo "Missing $total. Needs release-all.yml: ${manual:-none}"
# Not a failure HERE: a red plan skipped every build below (they need
# plan to succeed), so a release missing its amd64 zip did not get even
# the AppImages that could be made. The done job, at the end, is red
# for it instead.
- name: Say plainly what this run will not do
if: ${{ steps.plan.outputs.manual != '' }}
env:
STEP_PLAN_VERSION: ${{ steps.plan.outputs.version }}
STEP_PLAN_MANUAL: ${{ steps.plan.outputs.manual }}
run: |
echo "::error::v${STEP_PLAN_VERSION} still lacks ${STEP_PLAN_MANUAL} after recovery. Inspect the matching full-release run; older unnamed runs need their failed jobs retried manually."
exit 1
echo "::warning::v${STEP_PLAN_VERSION} still lacks ${STEP_PLAN_MANUAL} after recovery, which this workflow cannot build; the rest is built anyway. Inspect the matching full-release run; older unnamed runs need their failed jobs retried manually."
# The six architectures nobody else builds for, repacked from the PUBLISHED
# amd64 bundle - which is what makes this possible without a Meteor build.
@@ -517,6 +570,74 @@ jobs:
esac
echo "$mark charts" >> "$GITHUB_STEP_SUMMARY"
# wekan-ondra and wekan-gantt-gpl snaps the release lacks: the release's own
# wekan snap of that architecture under the variant's name and title
# (releases/snap-rename.sh) - what snap-variants builds from source, with
# nothing else changed. Releases before v13.21 have none attached.
variants:
permissions:
contents: write
name: variant snap ${{ matrix.variant }}
needs: plan
if: ${{ !cancelled() && needs.plan.result == 'success' && needs.plan.outputs.variant != '[]' }}
runs-on: ubuntu-24.04
timeout-minutes: 60
strategy:
fail-fast: false
matrix:
variant: ${{ fromJSON(needs.plan.outputs.variant) }}
env:
VERSION: ${{ needs.plan.outputs.version }}
VARIANT: ${{ matrix.variant }}
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Rename the release's wekan snap
id: rename
env:
GH_TOKEN: ${{ github.token }}
run: |
set -euo pipefail
name="${VARIANT%%:*}"
arch="${VARIANT#*:}"
case "$name" in
wekan-ondra) title='Wekan Ondra' ;;
wekan-gantt-gpl) title='Wekan Gantt GPL' ;;
*) echo "::error::'$name' is not a variant snap."; exit 1 ;;
esac
case "$arch" in *[!a-z0-9]*|'') echo "::error::'$arch' is not an architecture."; exit 1 ;; esac
sudo apt-get install -y squashfs-tools >/dev/null
mkdir -p source out
if ! gh release download "v$VERSION" --repo "$GITHUB_REPOSITORY" --dir source --pattern "wekan_${VERSION}_${arch}.snap"; then
echo "::error::v$VERSION has no wekan_${VERSION}_${arch}.snap to make $name from. Retry the release's snap job first (recover does), then run this again."
exit 1
fi
bash releases/snap-rename.sh "source/wekan_${VERSION}_${arch}.snap" "$name" "$title" out
- name: Attach it to the release
if: ${{ always() && steps.rename.outcome == 'success' }}
env:
GH_TOKEN: ${{ github.token }}
run: |
set -euo pipefail
bash releases/github-release-upload.sh "$GITHUB_REPOSITORY" "v$VERSION" out/*.snap
# Every snap of the release, in every channel of its snap name: the same
# "Push Snap to Store" that release-all.yml ends with. A revision the store
# already has is released by number; nothing is uploaded twice.
snap-store:
needs: [plan, variants]
if: ${{ !cancelled() && needs.plan.result == 'success' }}
permissions:
contents: read
uses: ./.github/workflows/snap-store.yml
with:
tag: v${{ needs.plan.outputs.version }}
snaps: wekan wekan-ondra wekan-gantt-gpl
channels: stable,candidate,beta,edge
secrets:
SNAP_AUTH: ${{ secrets.SNAP_AUTH }}
# The end of the run attaches nothing: every job above attached its own files
# as it finished them. This only reports what the release still lacks, and it
# runs on always() - not !cancelled() - so a cancelled run still says what
@@ -525,7 +646,7 @@ jobs:
done:
timeout-minutes: 15
name: what is still missing
needs: [plan, extra-arches, appimage, mac, flatpak, windows-exe, charts, bun]
needs: [plan, extra-arches, appimage, mac, flatpak, windows-exe, charts, bun, variants, snap-store]
if: ${{ always() && needs.plan.result == 'success' }}
runs-on: ubuntu-latest
steps:
@@ -566,3 +687,10 @@ jobs:
echo "::warning::v$V is still missing:${still}"
echo "Still missing:\`${still# }\`" >> "$GITHUB_STEP_SUMMARY"
fi
# What only release-all.yml can build, still missing: red here,
# once everything that could be built has been.
case " $still" in
*" meteor/"*|*" repack/"*|*" sandstorm/"*)
echo "::error::v$V still lacks what only release-all.yml builds:${still}. Inspect the matching full-release run."
exit 1 ;;
esac
+42
View File
@@ -5530,6 +5530,10 @@ jobs:
needs: [prepare, release, snap-auth-check]
continue-on-error: true
timeout-minutes: 90
# contents: write attaches the built snap to the GitHub Release; the
# workflow's default is read.
permissions:
contents: write
strategy:
fail-fast: false
matrix:
@@ -5655,6 +5659,7 @@ jobs:
echo "snap=$BUILT_SNAP" >> "$GITHUB_OUTPUT"
- name: Verify the built snap is ${{ matrix.snapname }}
id: verify
if: steps.guard.outputs.snap == 'true'
env:
STEP_BUILD_SNAP: ${{ steps.build.outputs.snap }}
@@ -5684,6 +5689,21 @@ jobs:
SNAP_UPLOAD_LABEL="${STEP_BUILD_SNAP}" \
bash "$GITHUB_WORKSPACE/wekan/releases/snap-upload-retry.sh" "${STEP_BUILD_SNAP}" stable,candidate,beta,edge
# always(): a built variant snap goes onto the GitHub Release even when the
# Snap Store push above failed. "Push Snap to Store"
# (.github/workflows/snap-store.yml) releases the snaps OF A GITHUB
# RELEASE to the store - and until v13.21 this job only uploaded to the
# store, so v13.20 had no wekan-ondra_*.snap or wekan-gantt-gpl_*.snap and
# that workflow failed with "no assets match the file pattern".
- name: Attach the ${{ matrix.snapname }} ${{ matrix.arch }} snap to the GitHub Release
if: ${{ always() && steps.verify.outcome == 'success' && steps.build.outputs.snap != '' }}
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
STEP_BUILD_SNAP: ${{ steps.build.outputs.snap }}
run: |
set -euo pipefail
bash "$GITHUB_WORKSPACE/wekan/releases/github-release-upload.sh" "${GITHUB_REPOSITORY:-wekan/wekan}" "v${VERSION}" "${STEP_BUILD_SNAP}"
# Always, as the last step: the run summary then answers "what worked and what
# did not" for the whole release at a glance, instead of eighteen job logs. A
# step that failed has already printed an ::error:: saying why; this names the
@@ -5710,6 +5730,28 @@ jobs:
# Refresh the selected changelog notes after builds. Binary provenance remains
# in build artifacts and is never appended to release notes.
# ─── Finish the Snap Store release of all three snaps ───────────────────────
# snap-native, snap-launchpad and snap-variants upload each snap with
# --release to every channel, but the store can keep a revision in
# "processing" for hours and then not release it: on v13.20 every snap job
# was green and the store kept the old version of wekan, wekan-ondra and
# wekan-gantt-gpl. This job takes the snaps those jobs attached to THIS
# release and releases each to stable, candidate, beta and edge - a revision
# the store already has by number, a missing one by uploading it - and is red
# when one did not get there. It also runs by hand as "Push Snap to Store".
snap-store:
needs: [prepare, snap-native, snap-launchpad, snap-variants]
if: ${{ !cancelled() && needs.prepare.result == 'success' }}
permissions:
contents: read
uses: ./.github/workflows/snap-store.yml
with:
tag: v${{ needs.prepare.outputs.version }}
snaps: wekan wekan-ondra wekan-gantt-gpl
channels: stable,candidate,beta,edge
secrets:
SNAP_AUTH: ${{ secrets.SNAP_AUTH }}
release-notes:
permissions:
contents: write
+58 -13
View File
@@ -15,8 +15,11 @@ name: Push Snap to Store
# processing, and FAILS - red, not green - when a snap still did not reach a
# channel.
#
# It runs after every "Release All Platforms" run, and by hand from the
# Actions tab for any release, snap names and channels.
# "Release All Platforms" calls it as its last snap job, for the tag it just
# released (its snap-store job), and it runs by hand from the Actions tab for
# any release, snap names and channels. It used to run on workflow_run after
# every Release All run and take "the latest release" - which, for a run that
# finished before its release was published, was the previous one (v13.20).
#
# Secrets: SNAP_AUTH, as for release-all.yml - an exported login carrying
# package_access, package_push, package_release and package_update for all
@@ -37,9 +40,22 @@ on:
description: 'Channels to release to'
required: false
default: 'stable,candidate,beta,edge'
workflow_run:
workflows: ['Release All Platforms']
types: [completed]
workflow_call:
inputs:
tag:
type: string
required: true
snaps:
type: string
required: false
default: 'wekan wekan-ondra wekan-gantt-gpl'
channels:
type: string
required: false
default: 'stable,candidate,beta,edge'
secrets:
SNAP_AUTH:
required: true
permissions:
contents: read
@@ -64,9 +80,9 @@ jobs:
id: plan
env:
GH_TOKEN: ${{ github.token }}
INPUT_TAG: ${{ github.event.inputs.tag }}
INPUT_SNAPS: ${{ github.event.inputs.snaps }}
INPUT_CHANNELS: ${{ github.event.inputs.channels }}
INPUT_TAG: ${{ inputs.tag }}
INPUT_SNAPS: ${{ inputs.snaps }}
INPUT_CHANNELS: ${{ inputs.channels }}
run: |
set -euo pipefail
tag="${INPUT_TAG:-}"
@@ -101,6 +117,7 @@ jobs:
sparse-checkout: releases
persist-credentials: false
- name: Install snapcraft and check SNAP_AUTH
id: snapcraft
env:
SNAP_AUTH: ${{ secrets.SNAP_AUTH }}
run: |
@@ -126,12 +143,29 @@ jobs:
run: |
set -euo pipefail
mkdir -p snaps
gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir snaps --pattern "${SNAP}_*.snap"
ls -l snaps
if ! ls snaps/"${SNAP}"_*.snap >/dev/null 2>&1; then
echo "::error::Release $TAG has no ${SNAP}_*.snap to push."
exit 1
# A release cut before v13.22 has no wekan-ondra or wekan-gantt-gpl
# snap attached (snap-variants did not attach them). A variant IS
# wekan with another name and title, so it is made from the
# release's wekan snaps (releases/snap-rename.sh), as Release All
# Missing does.
if ! gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir snaps --pattern "${SNAP}_*.snap"; then
case "$SNAP" in
wekan-ondra) title='Wekan Ondra' ;;
wekan-gantt-gpl) title='Wekan Gantt GPL' ;;
*) echo "::error::Release $TAG has no ${SNAP}_*.snap to push: its snap job did not attach one (snap-native and snap-launchpad attach wekan). Re-run that job of the release, or Release All Missing, then this workflow."; exit 1 ;;
esac
mkdir -p wekan-snaps
if ! gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir wekan-snaps --pattern "wekan_*.snap"; then
echo "::error::Release $TAG has neither ${SNAP}_*.snap nor a wekan_*.snap to make it from. Re-run the release's snap jobs, or Release All Missing, then this workflow."
exit 1
fi
sudo apt-get install -y squashfs-tools >/dev/null
for f in wekan-snaps/wekan_*.snap; do
bash releases/snap-rename.sh "$f" "$SNAP" "$title" snaps
done
echo "::notice::$TAG had no ${SNAP} snap; made it from the release's wekan snaps."
fi
ls -l snaps
- name: Push ${{ matrix.snap }} to the Snap Store, releasing to ${{ needs.plan.outputs.channels }}
env:
SNAPCRAFT_STORE_CREDENTIALS: ${{ secrets.SNAP_AUTH }}
@@ -148,3 +182,14 @@ jobs:
echo "::error::Not released:$failed. The ::error:: lines above say why."
exit 1
fi
# The newest revision the store has of each architecture, released to
# every channel too - one that reached the store some other way, or a
# reviewer approved later, whatever this release's files are. always():
# also when a file above was not taken.
- name: Release the newest ${{ matrix.snap }} revisions the store has to ${{ needs.plan.outputs.channels }}
if: ${{ always() && steps.snapcraft.outcome == 'success' }}
env:
SNAPCRAFT_STORE_CREDENTIALS: ${{ secrets.SNAP_AUTH }}
CHANNELS: ${{ needs.plan.outputs.channels }}
SNAP: ${{ matrix.snap }}
run: bash releases/snap-store-release-newest.sh "$SNAP" "$CHANNELS"
+258 -318
View File
@@ -95,6 +95,264 @@ Which databases WeKan supports
</details>
# v13.22 2026-11-20 WeKan ® release
**In short:** Repeating tasks of **Taskwarrior**, **Microsoft To Do**,
**Todoist**, **TickTick**, **Tasks.org**, **Vikunja**, **Super Productivity**,
**iCalendar**, **Org mode** and **Obsidian Kanban** now repeat in WeKan, and
their exports write the repeat back. **Release All**
builds and pushes **wekan**, **wekan-ondra** and **wekan-gantt-gpl** to every
Snap Store channel, and **Release All Missing** adds what a release lacks,
snaps included. A **WeKan board** imported from its own export keeps all of
its Board Settings and card fields, and **Rocket.Chat** and **Fizzy** are
imported and exported.
This release adds the following new features:
**Import and Export** - repeating tasks, the rest of an Org heading, and every
column of a table.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/24ac6b2bd2e55323fa1c6e52eb53ff3291fc80fb">A daily, weekly or monthly repeat becomes the card's recurrence, and is exported back</a>. Thanks to xet7.</summary>
WeKan cards can repeat daily, weekly or monthly, but no import set it and no
export wrote it: seven formats reported a repeat as lost and imported the task
once. `models/lib/recurrenceMap.js` reads iCalendar and TickTick RRULEs,
Taskwarrior `recur`, Org repeaters, Obsidian's and Todoist's "every week" and
Microsoft To Do patterns, and keeps a rule only when it is exactly daily,
weekly or monthly; every two weeks, yearly or a count stays in the import loss
report. An imported repeating card counts its last occurrence from the import,
so the recurrence job does not copy every card at once; of Taskwarrior's
instances only the newest open one repeats. The exports write it back
(Taskwarrior, Org mode, Obsidian Kanban, TickTick, the iCal feed), and the WeKan
JSON import keeps it. `tests/recurrenceMap.test.cjs`, with negative tests.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/878e53f418c2416796b5af00876ada7cc87a4161">Tasks.org, Vikunja and Super Productivity repeats become the card's recurrence too</a>. Thanks to xet7.</summary>
The Tasks.org RRULE and Vikunja's repeat_after (a day, a week) or repeat_mode
1 (monthly) are imported and written back; a Super Productivity task's repeat
config of every 1 day, week or month is imported. Other rules, and the repeat
of a finished task, stay in the import loss report. Google Tasks' API has no
repeat to read.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/55c3f574f4d0ba3fce3e507679b8c9d467feea46">Org mode keeps every property, uses :ID: as the card's reference and LOGBOOK clocks as its spent time</a>. Thanks to xet7.</summary>
Only :CREATED: was read from a heading's property drawer; the other
properties and the :LOGBOOK: drawer were dropped without a word in the import
loss report. Every other property is now a custom field, written back as a
property on export, and the closed CLOCK lines add up to the spent time. An
open clock, a malformed property line and any other drawer are reported.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/5b9fa791a82da0bcaa01e5b04f8e711c011580db">CSV, TSV and Excel imports keep every column, a column with no card field as a text custom field</a>. Thanks to xet7.</summary>
A column the header guess had no field for was imported only when ticked in
the mapping step, and dropped without a word otherwise - always for a REST
import. Every other named column now becomes a text custom field of its name,
ticked by default on the page; WeKan's own Number, Last activity and Voting
columns are not.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/95b88095c45bf582a2fdc3056cf5030f0b61e57a">OPML keeps created, category, links and an outliner's own attributes</a>. Thanks to xet7.</summary>
A card outline's created date, its categories, a link and any attribute of
the outliner's own (OmniOutliner's columns) were dropped or only reported.
Now they are the creation date, labels, a link in the description and custom
fields; the export writes created and the labels as category. An attribute of
a list or a checklist item is reported.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/3be07b147b46bcbe42f64da1170eda5fafcfe2ad">Leo keeps a card's creation date in its node id, both ways, and reports plugin data</a>. Thanks to xet7.</summary>
Leo stamps a node's id with the time it was made, and WeKan read it only as a
key and wrote ids without a time. The import now takes the creation date from
the id and the export writes it there; a Leo plugin's own data on a node is
reported instead of dropped.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/10caa20b094beae76ce941e609c7f130e6dd7d5f">Markdown reads and writes #tags, due dates and indented checkboxes as labels, due dates and checklists</a>. Thanks to xet7.</summary>
The import kept only a card's title, done mark and indented text, and the
export wrote no labels, dates or checklists. #tag words, Obsidian Kanban's
@{day} @@{time}, Obsidian Tasks' 📅 and todo.txt's due: are now labels and the
due date, and indented checkboxes the checklist, both ways.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/f467e31d176a2be66cfffecd87d9ac9938ff0d93">Slack, Mattermost, Telegram and Discord reactions become the imported comments' reactions</a>. Thanks to xet7.</summary>
Every reaction in a chat export was dropped without a word. An emoji, or a
Slack or Mattermost shortcode, is now kept as the comment's reaction for each
person mapped to a WeKan user; the loss report counts the reactions of people
not mapped and those of an emoji WeKan cannot store, such as a server's own
emoji or a skin tone.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/1122e49ca96930ac19f0431b514f68f7716da45a">Chat imports keep threads: a reply is a reply to the comment of the message it answers</a>. Thanks to xet7.</summary>
Slack, Mattermost, Telegram and Discord say which message a reply answers,
and the import made each reply a comment of its own. It is now a reply to that
comment, one level deep as WeKan's replies are; a reply to a message that is
not in the file stays a comment marked "↳".
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/28891103f6bec2d51e1dd1531103235d95a1a70c">Kanboard keeps its task recurrence, estimate, score, reference and external links, both ways</a>. Thanks to xet7.</summary>
WeKan's card recurrence was modelled on Kanboard's, and the import ignored it.
A repeat every 1 day, 7 days or 1 month now makes the card repeat, the
estimate, score and reference are custom fields, and external links are lines
of the description; the export writes them back.
</details>
- [Nextcloud Deck labels keep their colors instead of coming in black](https://github.com/wekan/wekan/commit/22d000b9136b11a4f8030d0e5d42e77518a70f64). Thanks to xet7.
- [OpenProject imports remaining time and exports spent time, which a round trip lost](https://github.com/wekan/wekan/commit/9bd503a71b22cfcf46c6e75e159c5bf0f5417331). Thanks to xet7.
- [ClickUp and GitLab exports write spent time, which their imports read and a round trip lost](https://github.com/wekan/wekan/commit/14afc74adbb6659ee3a8f57ebe84999b439557c6). Thanks to xet7.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/1a02de4b5b398018bbe2076d98cba10b01639e5a">Exports are held to what their imports read back; Asana time, Deck done ticks, Kanboard colors survive</a>. Thanks to xet7.</summary>
A new test exports a card with every field set in 32 formats, reads the file
back and holds each format to what it keeps of dates, spent time, the done
tick, recurrence, people, custom fields and color. It found Asana's time
tracking read and written by neither side, Deck's done tick lost without an
end date, and Kanboard colors not written; all three are fixed.
</details>
- [Asana's html_notes, approval states and comment likes come across](https://github.com/wekan/wekan/commit/57a657445ef63cc979530f04585227d778c01845). Thanks to xet7.
- [Planka 2 custom fields and stopwatch time come across](https://github.com/wekan/wekan/commit/0d65eec4f2f36ba6df3b0fcf2d26aa023a02fa75). Thanks to xet7.
- [Imported subtasks keep their due date and person on the checklist item (Google Tasks, KanbanFlow)](https://github.com/wekan/wekan/commit/cf6f67e789ac404866d4b51591820570850baaa3). Thanks to xet7.
- [Basecamp card steps keep their due date and assignee](https://github.com/wekan/wekan/commit/a72b29726821301db304b4120bcc21566650202a). Thanks to xet7.
- [Notion relations between rows of an export become "related to" dependencies](https://github.com/wekan/wekan/commit/f546ff238345dd267e568d75ce1fe25bf4fdbbb7). Thanks to xet7.
- [ClickUp custom field columns come across both ways, and the task link is kept](https://github.com/wekan/wekan/commit/60f569afe679ffcf6bdfe36f16d4d2bb42f07502). Thanks to xet7.
- [Todoist and TickTick imports report a column they do not write, instead of dropping it](https://github.com/wekan/wekan/commit/c72a05d11a7527a0b0cb1855de8609de4217faa2). Thanks to xet7.
- [Taiga's blocked state is the card's Blocked flow field, both ways](https://github.com/wekan/wekan/commit/ab884547f44913cb5269b8248e6301b4983a43c0). Thanks to xet7.
- [Linear cycles become Scrum sprints and project milestones Scrum releases](https://github.com/wekan/wekan/commit/75694ac644d71016b092c0543a62fb63aef817ee). Thanks to xet7.
- [Telegram and Discord imports bring their message files from a zipped export folder](https://github.com/wekan/wekan/commit/828ca63713b0a034c9e1c436341cd60435c01443). Thanks to xet7.
- [Slack import downloads the messages' files with a Slack token, from Slack's file host only](https://github.com/wekan/wekan/commit/dd8242b82ffe97bb760471a3677550632d72a4d8). Thanks to xet7.
- [Super Productivity export writes a repeating card's repeat config, so it repeats there too](https://github.com/wekan/wekan/commit/35f3f6c9dbec5de87e1181956ed7bf71c30a2f12). Thanks to xet7.
- [GitHub, Gitea and Forgejo keep an issue's dates, people and Gitea's time estimate, both ways](https://github.com/wekan/wekan/commit/efeb55f57a903a80ab7b6ee124a87f9ce39bdf00). Thanks to xet7.
- [GitHub's issue type is kept as a "type:" label](https://github.com/wekan/wekan/commit/9ceb4dbf55ecb2518c64d449b9d6d06703b961a9). Thanks to xet7.
- [GitLab issue health status and incident severity are kept as labels](https://github.com/wekan/wekan/commit/c916b154731084d1a9e7674852575a205ff68a66). Thanks to xet7.
- [Planner imports read the newer "Export as Excel" column names too](https://github.com/wekan/wekan/commit/d3aa34e7b8f5d579fabb0e4df9f06710493fd1f2). Thanks to xet7.
- [GitHub, Gitea, Forgejo and GitLab imports count reactions in the loss report, which are counts without who reacted](https://github.com/wekan/wekan/commit/1b9ec7b9a1ba12f83969379ec059dd9bd5ec5c3a). Thanks to xet7.
**Rocket.Chat and Fizzy** - two more tools, imported and exported.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/dffbafd30fd16978dbae49a4e0d576bb1ff017ec">Rocket.Chat exports are imported for the Chat view, and a board exports for its CSV importer</a>. Thanks to xet7.</summary>
Read from Rocket.Chat's source: "Download my data" as JSON is a .zip of
`channels.json` and a message file per room with the files under `assets/`;
one room's `.json` and the .zip its CSV importer reads are imported too. A room
is a card in Channels, Groups, Direct messages or Omnichannel, its messages the
comments, its files the attachments; system messages and missing files are
counted. The export writes `users.csv`, `channels.csv` and a `messages.csv` per
card, with no header rows and names Rocket.Chat accepts.
`tests/chatExportFormats.test.cjs` reads both zips and round-trips the export.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/dffbafd30fd16978dbae49a4e0d576bb1ff017ec">Fizzy's account and personal data exports are imported, and a board exports as its account export</a>. Thanks to xet7.</summary>
Read from Fizzy's source (37signals). A Fizzy board is a swimlane, its columns
lists between Maybe?, Not now and Done; tags, assignees, steps, comments,
golden cards and files come along, drafts and reactions are counted. The
export is `data/<table>/<id>.json` with every column Fizzy's account import
requires, base36 UUIDv7 ids and only users of the export, so Fizzy reads it
back. `tests/fizzyFormat.test.cjs` checks those columns and round-trips it; the
Playwright round trip sends it through the server.
</details>
and fixes the following bugs:
**WeKan import** - a board exported and imported back.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/c640c5c376526f6550873b757fa6b68511c63d42">A WeKan board imported from its own export keeps every Board Settings choice and every card field</a>. Thanks to xet7.</summary>
The export writes the whole board and its cards, and the import wrote 32 of
the 210 board fields and about 30 of the 87 card fields: every Board Settings
choice came back at its default, and cards lost their flow fields, votes,
planning poker, stickers, locations, drawings and more. They are all written
now, users mapped to the new board's; access and inbound email are left to
the new board's admin, and a value the schema refuses is reported.
`tests/wekanCardFields.test.cjs` holds the lists to the schemas.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/24b6b9b0247bf1cda039faec6dba9298f9115116">It also keeps the lists' WIP limits and policies, checklist settings, custom field access and comment replies</a>. Thanks to xet7.</summary>
A list lost its WIP limit, flow policy and split, a swimlane its height, a
checklist its hide settings and reset schedule, an item its assignee, a reply
its comment - and a custom field its "admin only" and "read only", which left
it open to everyone on the imported board. All of them come back now; a list
role exception is kept only where it restricts a role.
</details>
- [Templates stay templates: a WeKan template board, card, list or swimlane imports as one](https://github.com/wekan/wekan/commit/a4359731b1bed397e1616dd8289b0d437f8e7243). Thanks to xet7.
and has the following developer-facing changes:
**Snap packages** - all three snap names, on every channel.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/dc0a1ad049f19fd8557dfde81e2de948b601f999">Release All ends by pushing all three snaps of its release; Release All Missing makes and pushes the missing ones</a>. Thanks to xet7.</summary>
Push Snap to Store failed for v13.20: snap-variants never attached
wekan-ondra and wekan-gantt-gpl to the GitHub Release, a store-side "Error
checking upload uniqueness" was waited on for two hours instead of uploaded
again, and the workflow took "the latest release", the previous one. Now
snap-variants attaches its snaps, `releases/snap-store-push.sh` retries store
failures and fails at once on any other refusal, and Release All calls Push
Snap to Store for the tag it released. Release All Missing lists the snaps as
release assets, makes a missing variant from the release's own wekan snap
(`releases/snap-rename.sh`, name and title only), pushes the release's snaps,
and with no version starts one run per incomplete release.
`tests/snapStorePush.test.cjs`.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/ce646dc937689f4ff84049e3af9b73ebeff9ef07">Push Snap to Store releases what the store already has, each channel on its own, and uploads a file once</a>. Thanks to xet7.</summary>
snapcraft 9 renamed list-revisions to revisions, so the push never found the
revision the store already had and uploaded the same file again and again,
answered "Error checking upload uniqueness". It now reads the store's
revisions, releases one it has instead of uploading, uploads a file once,
releases to each channel on its own so one refusal does not stop the others,
and also releases the newest revision of every architecture the store holds.
A revision held for the store's manual review ("ReviewQueued") is reported
with how to ask for the review. Release All and Release All Missing run the
same steps.
</details>
Thanks to above GitHub users for their contributions and translators for their translations.
# v13.21 2026-11-20 WeKan ® release
**In short:** Twelve new **Board View reports** - Created vs. Resolved, Net
@@ -8329,321 +8587,3 @@ Panel / People.
</details>
Thanks to above GitHub users for their contributions and translators for their translations.
# v12.52 2026-10-18 WeKan ® release
**In short:** the release builds that failed in v12.51 work again: the
**Android** bundles, the **musl AppImages** and the **i386** and
**freebsd-x64** single files. Nine dependency updates, among them
**qrcode-generator 2** and **actions/download-artifact 8**, were checked
against how WeKan uses them.
This release updates the following dependencies:
- **qrcode-generator 1.4.4 → 2.0.4** — [the SQRL sign-in QR
code](https://github.com/wekan/wekan/pull/6775); now ES module and CommonJS
builds, and the SVG of WeKan's call is byte for byte the same.
- **temml 0.13.5 → 0.14.0** — [math in
Markdown](https://github.com/wekan/wekan/pull/6777); WeKan's
`renderToString` options give the same output for formulas, errors and
`\href`.
- **i18next 26.4.2 → 26.4.5** — [the translation
library](https://github.com/wekan/wekan/pull/6779).
- **@swc/core 1.16.13 → 1.16.18** — [the compiler of the
build](https://github.com/wekan/wekan/pull/6778).
- **@rspack/cli 2.2.8 → 2.2.9** — [the bundler's command
line](https://github.com/wekan/wekan/pull/6773).
- **@playwright/test 1.63.0 → 1.64.1** — [the browser
tests](https://github.com/wekan/wekan/pull/6776).
- **actions/download-artifact 7.0.0 → 8.0.2** — [in five
workflows](https://github.com/wekan/wekan/pull/6774); a hash mismatch now
fails the download, and every artifact WeKan uploads is still a zip.
- **actions/setup-python 6.3.0 → 7.0.0** — [in
bun.yml](https://github.com/wekan/wekan/pull/6780); the removed `pip-install`
input was not used.
- **vmactions/freebsd-vm 1.5.5 → 1.5.9** — [in
bsd.yml](https://github.com/wekan/wekan/pull/6781), the version bun.yml
already uses.
Thanks to dependabot.
and fixes the following bugs:
**Release builds** - the Android, musl and single-file builds of v12.51, and
the guards of the dependency updates.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/53729d47f5">The guards follow freebsd-vm 1.5.9 and qrcode-generator 2.0.4</a>. Thanks to dependabot and xet7.</summary>
Two tests stopped at the merged updates. `tests/bsdBundles.test.cjs` pinned
`bsd.yml`'s FreeBSD VM action to its old commit, because the VM that builds
the bundle's native modules must be the one that built node-freebsd-x64. It
now reads the pin and requires wekan/node-patches to use the same commit, and
node-patches now does. `tests/sqrl.test.cjs` required qrcode-generator 1.4.4
exactly, and now requires an exact version.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/0670cc65a3">Android bundles: the checkout belongs to Termux's user, so npm may chmod</a>. Thanks to xet7.</summary>
Every Android bundle of v12.51 stopped with EPERM. npm chmods each package's
bin when it installs (`uuid/dist/bin/uuid`), and only a file's owner may
chmod it, so making the bind mount writable to everyone (`a+rwX`) was not
enough. `android.yml` now reads the uid of Termux's user from the image,
chowns the checkout to it before the rebuild, and takes it back before
packaging. If it cannot read the uid, it stops the job.
`tests/androidBundles.test.cjs` pins the order and the negative case.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/bce305029a">musl bundles carry libstdc++ and libgcc_s, so their Node.js starts on a bare Alpine</a>. Thanks to xet7.</summary>
Every musl AppImage of v12.51 died at once in Alpine with "Error relocating
.../bundle/node: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found".
The musl Node.js is linked against GCC's C++ runtime. The Alpine that
`musl.yml` builds in had it installed, and a user's Alpine does not. The
bundle's `node-runtime` now holds that Alpine's `libstdc++.so.6` and
`libgcc_s.so.1`, with a license notice. `start-wekan.sh` puts them on the
library path, as it does with libatomic, and the AppImage workflow requires
both files in a musl bundle. Its smoke test still adds only curl to Alpine,
so `tests/muslBundles.test.cjs` would catch this fault again.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/c316616ef8">Single files: a Node.js that LIEF cannot inject is skipped with the reason, not failed</a>. Thanks to xet7.</summary>
The v12.51 i386 single file stopped with `std::bad_alloc`, and the
freebsd-x64 one with "Failed to relocate ELF program headers". Node.js
injects the archive with LIEF:
- The i386 Node.js is a PIE with 1,524 R_386_32 relocations, which LIEF does
not adjust. postject, which uses the same LIEF, "succeeds" and leaves a
broken binary.
- The FreeBSD Node.js is a non-PIE with two bss-like segments.
`releases/single-file/sea-inject.mjs` detects both from the ELF before
anything is built. `build.mjs` then exits 3 with the reason, which
`single-file.yml` turns into a notice. wekan/node-patches now builds the
i386 Node.js as a non-PIE and the FreeBSD one as a PIE, so both single files
come back with its next release. A target that was not built leaves a
one-line artifact saying why, so its Start job no longer logs "Artifact not
found" errors. `tests/singleFileSeaInject.test.cjs` checks both cases on
synthetic ELF files, and its negative cases let through what LIEF does
inject.
</details>
Thanks to above GitHub users for their contributions and translators for their translations.
# v12.51 2026-10-17 WeKan ® release
**In short:** eleven **helpers that need no AI** - features other kanban
apps sell as AI, done here with plain code: a **due date from the title**,
**similar cards**, **rule suggestions**, a board **Summary**, **Since your last
visit**, **At risk**, **suggested members**, a **forecast done date**, a
**checklist from the description**, **action items** and **search phrases**.
A card's drawing also opens as a **whiteboard** that several people draw on
at once, and **Apple Glass Pastel** is now Liquid Glass. Each can be hidden
per board or for the whole WeKan. A **CodeQL** alert in a test is fixed.
This release fixes the following SECURITY ISSUES found by GitHub CodeQL code scanning:
<details>
<summary><a href="https://github.com/wekan/wekan/commit/6090be4dfd">Alert #588: a test removes template declarations to a fixed point</a>. Thanks to GitHub CodeQL and xet7.</summary>
js/incomplete-multi-character-sanitization in
tests/templatesAreRendered.test.cjs: one replace each removed template
declarations and Template.<name>.helpers/onCreated/... from the source the
test scans, so removing one could splice its neighbours into another. Both
now repeat until nothing changes, as for alerts #545 and #570-#582, and
tests/tagStrippingFixedPoint.test.cjs now also finds a multi-character removal
of an on<Capital> name outside such a loop anywhere in the tree. A test's
source scan, never run on user input, so nothing reaches Admin Panel ->
Problems.
</details>
and adds the following new features:
**Helpers that need no AI** - computed from the board's own data, hidden like
every other optional part, and translated in every language.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/f8267d704e">A due date typed at the end of a card title becomes its due date</a>. Thanks to xet7.</summary>
"Call the printer tomorrow 14:00", "Soita huomenna klo 14", "friday 9:30",
"in 3 days" or "23.10." at the end of a new card's title gives the card that
due date, and the words leave the title. The words come from the browser's
own Intl tables (relative days, weekdays, the language's date order and the
word before a time), so every language works without a word list, and English
works in every language. Only the end of the title is read, a time alone needs
a colon, a day word or am/pm, and "Release 1.2" is never a date. A hint under
the field shows the date and its x keeps the words; the opened card's title
reads it only when the title changed. Board Settings / Card row *Due date
from title*. models/lib/titleDueDate.js; tests/titleDueDate.test.cjs checks
eleven languages, the negatives and every WeKan language tag, and
assist-due-from-title.e2e.js the form, the x, the board switch and the
opened card.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/f8267d704e">Similar cards and possible duplicates while adding a card and on the opened card</a>. Thanks to xet7.</summary>
Letter triples and the Dice coefficient - letter pairs for scripts written
without spaces - rank the board's open cards against the title being typed or
the opened card's title and description. The add-card form lists up to three,
marking one 80 % alike or more as a possible duplicate; the opened card has a
Similar cards section. The method cards.similar reads through
server/lib/assistGate.js: a board the caller may read, the board's switch and
the Admin Panel's, and for an assigned-only member only the cards assigned to
them. tests/similarCards.test.cjs and assist-similar-cards.e2e.js, with the
assigned-only and switched-off negatives.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/2211b24119">Rules suggests rules from what people keep doing by hand</a>. Thanks to xet7.</summary>
When the same person does one thing to a card and within two minutes
another, the pair is counted once per card; seen on three cards in 30 days it
is offered above the rule list - moved to a list then a label, a member or
archive, and so on. A pair a rule already does is not offered. Create goes
through rules.createRule with the trigger and action the wizard builds, and
Dismiss hides one for that admin on that board. Board admins only, and
Admin Panel / Settings / Visibility / Features has a Rule suggestions tick.
tests/ruleSuggestions.test.cjs and assist-rule-suggestions.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/083c863fb7">Board menu: Summary, what each person did in the last day or week</a>. Thanks to xet7.</summary>
Per person: done (marked complete, given an end date, archived or moved into
the last list), moved, added, commented, and what they have overdue now -
from the activities and History, only the cards the reader may see. Copy as
text gives Markdown with card links. An Admin Panel / Settings / Visibility /
Features tick. tests/boardSummary.test.cjs and assist-board-summary.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/083c863fb7">Board menu: Since your last visit, with how many changes</a>. Thanks to xet7.</summary>
What others changed since the visit before this one, grouped by card. Opening
a board remembers the visit in profile.boardVisits (500 boards at most) even
while the feature is hidden; a board never opened shows its last seven days.
tests/sinceLastVisit.test.cjs and assist-since-last-visit.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/083c863fb7">At risk: a triangle on the minicard and the reasons in the opened card</a>. Thanks to xet7.</summary>
A weighted score: overdue 3, due within two days with less than half the
checklist done 2, blocked by an open card 2, idle 14 days in a middle list
2, moved back twice 1 (the opened card counts those). 3 or more is at risk;
a complete card never is. models/lib/cardRisk.js; tests/cardRisk.test.cjs and
assist-at-risk.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/083c863fb7">Suggested members in the Members and Assignees popups</a>. Thanks to xet7.</summary>
Up to three active board members, by points from the board's open cards that
share this card's labels (2 each), list (1) and swimlane (1); people already
on the card are skipped. A Show on Card row only, the one row with no
minicard side. tests/memberSuggestions.test.cjs and
assist-suggested-members-forecast.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/083c863fb7">Forecast done date for one card, 50 % and 85 %</a>. Thanks to xet7.</summary>
From the cycle times of the board's cards finished in 180 days, counting only
those that took at least as long as this card has been open; fewer than five
say so. The server sends the times once per board, numbers only, scoped by
role. On the opened card's dates, and on the minicard when a board turns that
side on. tests/cardForecast.test.cjs and the e2e above.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/3cb089b8ca">Checklists: From description makes a checklist or subtasks from its list</a>. Thanks to xet7.</summary>
The description's list lines - "- ", "* ", "+ ", "1. ", "1) " and task boxes,
never inside a code block - are previewed, then made into a checklist ticked
where the line was [x], or into subtasks through addSubtaskCard. The
description is not changed. tests/descriptionListItems.test.cjs and
assist-from-text.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/3cb089b8ca">Cards from the action items of a comment or a description</a>. Thanks to xet7.</summary>
"TODO: ...", "- [ ] ..." and "@user ..." lines become cards at the top of the
card's list, each linking back to the card, with the mentioned user as member
when they are an active board member - a mention of anybody else stays in the
title. On the comment's line, and in the card menu for the description.
tests/actionItems.test.cjs and assist-from-text.e2e.js.
</details>
<details>
<summary><a href="https://github.com/wekan/wekan/commit/3cb089b8ca">Global search understands plain phrases such as my overdue cards</a>. Thanks to xet7.</summary>
Ten phrases in the reader's language, and in English everywhere, run as the
search operators in the reader's language; the page shows the query it ran,
and a query that already has an operator is never rewritten. An Admin Panel /
Settings / Visibility / Features tick. tests/searchPhrases.test.cjs and
assist-search-phrases.e2e.js.
</details>
**Apple Glass Pastel** - the theme as Apple's Liquid Glass, readable everywhere.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/0c49f7f51b">Liquid Glass surfaces, and every text and icon measured readable</a>. Thanks to xet7.</summary>
Header bars, swimlanes, lists, minicards, the opened card, the sidebar and
popups are frosted glass over the pastel mesh: a translucent fill, blur and
saturation, a rim of light brightest on top, a diagonal sheen and larger
corners. The header bars are glass instead of solid blue, with dark text;
blue stays for the primary action and what is active. Reduce transparency
gets near-opaque surfaces. theme-appleglasspastel-contrast.e2e.js measures
every text and icon against the pixels really behind it, to WCAG AA, on the
board, card, sidebar, board menu and All Boards at laptop and phone size; it
found white header text and icons, the forced-white hamburger, grey sidebar
headings and icons, and a white hovered menu row, all fixed.
</details>
**Whiteboard** - a card's drawing full screen, for several people at once.
<details>
<summary><a href="https://github.com/wekan/wekan/commit/390007e380">A card's drawing opens as a whiteboard that several people draw on at once</a>. Thanks to xet7.</summary>
Card menu -> Drawing -> Open as whiteboard: the drawing under the header bar,
over the opened card, with the drawing's and Red Strings' own colours, widths,
Undo, Clear and Save picture, scaled to the screen. Each line is one atomic
$push with its id and author, carried to everyone by the card's publication;
Undo and Clear take away only one's own lines, Save picture writes only the
PNG. Who may draw is who may edit the card. A Board Settings / Card row.
tests/whiteboard.test.cjs, and whiteboard.e2e.js draws from two browsers at
the same moment.
</details>
and improves the documentation:
- [docs/Features: guides for the eleven helpers that need no AI, filed by menu](https://github.com/wekan/wekan/commit/e76f12bcdd),
and TODO Later lists them. Thanks to xet7.
- [docs/Features: Cards / Whiteboard](https://github.com/wekan/wekan/commit/d9bb7b4f4f). Thanks to xet7.
Thanks to above GitHub users for their contributions and translators for their translations.
+14 -11
View File
@@ -5,6 +5,20 @@ each one changed and the project status are in
Written by `node releases/changelog-short.mjs` from CHANGELOG-big.md:
make changes there.
# v13.22 2026-11-20 WeKan ® release
Repeating tasks of **Taskwarrior**, **Microsoft To Do**,
**Todoist**, **TickTick**, **Tasks.org**, **Vikunja**, **Super Productivity**,
**iCalendar**, **Org mode** and **Obsidian Kanban** now repeat in WeKan, and
their exports write the repeat back. **Release All**
builds and pushes **wekan**, **wekan-ondra** and **wekan-gantt-gpl** to every
Snap Store channel, and **Release All Missing** adds what a release lacks,
snaps included. A **WeKan board** imported from its own export keeps all of
its Board Settings and card fields, and **Rocket.Chat** and **Fizzy** are
imported and exported.
[All changes in v13.22](CHANGELOG-big.md#v1322-2026-11-20-wekan--release)
# v13.21 2026-11-20 WeKan ® release
Twelve new **Board View reports** - Created vs. Resolved, Net
@@ -44,14 +58,3 @@ problems: 1" and "Checks with findings: 8 / 31", in every language - and a
report row's address, location and user always belong to the same occurrence.
[All changes in v13.18](CHANGELOG-big.md#v1318-2026-11-19-wekan--release)
# v13.17 2026-11-19 WeKan ® release
The **Admin Panel** answers one question per tab: Settings gains
**Appearance**, **Features**, **Feature profiles**, Security, Activities and
notifications, and Delete, Problems keeps only what is going wrong, and every
old
address redirects. The docs now have a page for every menu entry, and cards of
an archived swimlane no longer appear in the first swimlane.
[All changes in v13.17](CHANGELOG-big.md#v1317-2026-11-19-wekan--release)
+1 -1
View File
@@ -38,7 +38,7 @@ FROM --platform=$BUILDPLATFORM debian:trixie AS bundle
ARG TARGETARCH
ARG TARGETVARIANT
ARG VERSION=13.21
ARG VERSION=13.22
ARG DEBIAN_FRONTEND=noninteractive
COPY --chmod=755 releases/check-telemetry.py /tmp/check-telemetry.py
+3 -3
View File
@@ -44,10 +44,10 @@ that by providing one-click installation on various platforms.
- Add Board / Import ([all import and export formats](docs/Features/Board-Sidebar/Board-Settings/Import-Export/External-Tools.md)):
- WeKan JSON/.zip, CSV/TSV, Excel, Markdown, Obsidian Kanban, Leo, OPML, Org mode, todo.txt
- Trello, Jira, Asana, Zenkit, Focalboard, Todoist, Microsoft Planner, MeisterTask, Linear, TickTick, ClickUp, Nullboard, Kanri, Pivotal Tracker, Redmine, Tasks.org, monday.com,
Super Productivity, Taiga, Vikunja, Wrike (Excel and workflow), Quire, Teamwork.com, Businessmap, Notion, Plane
Super Productivity, Taiga, Vikunja, Wrike (Excel and workflow), Quire, Teamwork.com, Businessmap, Notion, Fizzy, Plane
- Kanboard, Nextcloud Deck, OpenProject, Taskwarrior, Planka, KanbanFlow, Basecamp, Microsoft To Do, Google Tasks
- Mail (.eml/mbox), Calendars (iCalendar), Google Takeout, Google Keep, Evernote,
Chats: Slack, Mattermost, Telegram, WhatsApp, Discord - each into the view it fits
Chats: Slack, Mattermost, Rocket.Chat, Telegram, WhatsApp, Discord - each into the view it fits
- Large files are streamed to disk, within its free space or the Admin Panel limit
- GitHub, GitLab, Gitea, Forgejo
- Import many boards at once: several export files, or a .zip of them, each its own board;
@@ -105,7 +105,7 @@ that by providing one-click installation on various platforms.
Microsoft Planner, MeisterTask, Obsidian Kanban, Linear, TickTick, ClickUp, Nullboard, Kanri, Pivotal Tracker, Redmine, Tasks.org, monday.com,
Super Productivity, Taiga, Vikunja, Wrike (Excel and workflow), Quire, Teamwork.com, Businessmap, Notion,
Trello, Jira, NextCloud Deck, OpenProject, GitHub, GitLab,
Gitea, Forgejo, Asana, Zenkit, Trello .zip with attachments, mbox, Evernote, Mattermost
Gitea, Forgejo, Asana, Zenkit, Trello .zip with attachments, mbox, Evernote, Mattermost, Rocket.Chat, Fizzy
- Every export is written a page of cards at a time, so a large board exports without running out of memory
- Export all boards at once (All Boards sidebar, or Multi-Selection): Excel as one workbook
with a sheet per board, every other format as a .zip with a file per board
+1 -1
View File
@@ -1,5 +1,5 @@
appId: wekan-public/apps/77b94f60-dec9-0136-304e-16ff53095928
appVersion: "v13.21.0"
appVersion: "v13.22.0"
files:
userUploads:
- README.md
+33 -39
View File
@@ -20,44 +20,38 @@ the changelog only says what changed.
- The WebKit stage cannot run in the Flatpak sandbox: MiniBrowser needs its own
sandbox, and turning that off is not allowed there. Run it on a host.
## Import and Export of everything each tool has
## Need accounts on the tools, or a running copy of one
Asked on 2026-11-20: check and fix that everything each tool with a WeKan
import or export can hold comes across, whether a whole export is read or
written at once or only a part of it (a board, a project, some lists, a date
range), and check each tool's newest features - what its current version
exports and imports - so their data has a place in WeKan too. For every tool,
compare its newest export file, documentation and changelog with the parser
and the formatter here, record what is lost in the import loss report
(`unsupported`), and add what has a place in WeKan.
The import/export review asked on 2026-11-20 (everything each tool with a
WeKan import or export can hold comes across, whole or in part) went through
every parser and formatter against the export format its header documents.
What it found is fixed and in the Upcoming release; the round trips are held
by `tests/playwright/specs/export-import-round-trip.e2e.js` (41 formats, the
description, checklist, comment, dependency, label and due date) and
`tests/exportRoundTripFields.test.cjs` (32 formats in plain Node: start and
creation dates, spent time, the done tick, recurrence, people, custom fields,
color, Blocked), and a WeKan board's every field by
`tests/wekanCardFields.test.cjs`. What is left needs what this checkout does
not have:
Done so far: `tests/playwright/specs/export-import-round-trip.e2e.js` exports
a board in each of the 41 formats WeKan both writes and reads and imports the
file back; every one brings the card back, and its KEEPS table holds each
format to what its file keeps of the description, the checklist and the
comment, so a format that loses more fails. The Trello export imports back
with checklists, comments, members, custom fields and archived cards and
lists, and a Trello .zip export carries the attachment files; the GitHub,
Gitea and Forgejo exports carry the comments. What is left below is per tool: the
tool's newest features against its parser and formatter.
- WeKan's own JSON and .zip: every field of the current schema, attachments
and their versions, custom fields, rules, templates, Scrum data, and a part
of a board as well as all of it.
- Kanban and project tools: Kanboard, Nextcloud Deck, OpenProject, Asana,
Zenkit, Planner, monday.com, Wrike, Teamwork, Businessmap, ClickUp, Notion,
Plane, Taiga, Focalboard, Nullboard, Kanri, Obsidian Kanban, MeisterTask,
Quire, Planka, KanbanFlow, Basecamp - sub-items, dependencies, time
tracking, custom fields, comments, attachments and their newer views.
- Issue trackers: Jira, GitHub, GitLab, Gitea, Forgejo, Redmine, Linear,
Pivotal - epics, sprints, versions and milestones, links between issues,
work logs, reactions, and fields added in their newest releases.
- Task tools: Todoist, TickTick, Tasks.org, Super Productivity, todo.txt,
Taskwarrior, Vikunja, Microsoft To Do, Google Tasks, Google Keep -
recurrence, reminders, priorities, sub-tasks and sections.
- Spreadsheets, text and outlines: CSV / TSV, Excel, Markdown, Leo, OPML,
Org mode - every column, and every Org property and timestamp.
- Mail, calendars and chats: mail, mbox, iCalendar, Google Takeout, Slack,
Mattermost, Telegram, WhatsApp, Discord, Evernote .enex - threads, replies,
reactions, recurring events and the attached files that are now only
counted.
- Each tool's newest release, checked with a real export file of it: Planner,
Wrike, Teamwork, Businessmap, MeisterTask, Quire and Jira - the
proprietary ones, whose current export is only seen with an account
(Planner's newer Status, Task title and Assignments columns are read, as
Microsoft's help page names them; a real file would confirm their exact
spelling). The parsers follow
the formats the tools document and report what they do not read, so a new
field shows up in the import's loss report; checking for one needs an
account on each tool. (Checked against their current source on 2026-11-20:
Plane's IssueExportSerializer, Kanri's kanban-types.d.ts, Obsidian Kanban's
markers, Nullboard's board object, and Gitea's (and Forgejo's) Issue
struct, whose created_at, closed_at and time_estimate are read now;
GitHub's REST issue, whose issue type is read now; GitLab's Issues API v4,
whose health status and incident severity are read now. Redmine and
monday.com import every column they do not name as a custom field, so a
column a new release adds comes across without a change. Focalboard's archive
format is frozen: Mattermost stopped merging changes to Focalboard and
Boards in September 2023.
Pivotal Tracker was shut down in 2025, so there is no newer release.
Linear's open-source importer, @linear/import, declares the columns the
parser reads.)
+2 -2
View File
@@ -2029,11 +2029,11 @@ if arguments >= 3 and sys.argv[1] == 'exportboardpdf':
# { excelBase64 } (Plane's as { xlsxBase64 }), an export .zip as { zipBase64 },
# a CSV/TSV file as rows, a text format as its text, and the rest as JSON.
EXCEL_IMPORT_SOURCES = {'excel', 'planner', 'monday', 'wrike', 'teamwork', 'businessmap'}
ZIP_IMPORT_SOURCES = {'vikunja', 'notion', 'plane', 'slack', 'googletakeout'}
ZIP_IMPORT_SOURCES = {'vikunja', 'notion', 'plane', 'slack', 'googletakeout', 'telegram', 'discord', 'rocketchat', 'fizzy'}
TEXT_IMPORT_SOURCES = {'markdown', 'todotxt', 'taskwarrior', 'focalboard', 'todoist', 'meistertask', 'obsidian',
'linear', 'ticktick', 'clickup', 'nullboard', 'pivotal', 'redmine', 'superproductivity',
'quire', 'orgmode', 'leo', 'opml', 'vikunja', 'notion', 'plane',
'mail', 'ical', 'mattermost', 'whatsapp', 'evernote', 'slack', 'googletakeout'}
'mail', 'ical', 'mattermost', 'whatsapp', 'evernote', 'slack', 'googletakeout', 'rocketchat', 'fizzy'}
def import_document(source, filepath):
import base64, csv, io, os
+2
View File
@@ -249,6 +249,7 @@ const EXPORT_FORMAT_GROUPS = [
{ key: 'mbox', icon: 'fa-envelope-o', label: 'Mail (mbox)', path: 'export/mbox', ext: 'mbox', scopes: BOARD_ONLY },
{ key: 'enex', icon: 'fa-sticky-note', label: 'Evernote (.enex)', path: 'export/enex', ext: 'enex', scopes: BOARD_ONLY },
{ key: 'mattermost', icon: 'fa-comments', label: 'Mattermost', path: 'export/mattermost', ext: 'jsonl', scopes: BOARD_ONLY },
{ key: 'rocketchat', icon: 'fa-comments', label: 'Rocket.Chat', path: 'export/rocketchat', ext: 'zip', scopes: BOARD_ONLY },
{ key: 'todotxt', icon: 'fa-list-ul', label: 'todo.txt', path: 'export/todotxt', ext: 'txt', scopes: BOARD_ONLY },
{ key: 'taskwarrior', icon: 'fa-terminal', label: 'Taskwarrior', path: 'export/taskwarrior', ext: 'json', scopes: BOARD_ONLY },
{ key: 'focalboard', icon: 'fa-th-large', label: 'Focalboard', path: 'export/focalboard', ext: 'jsonl', scopes: BOARD_ONLY },
@@ -267,6 +268,7 @@ const EXPORT_FORMAT_GROUPS = [
{ key: 'monday', icon: 'fa-table', label: 'monday.com', path: 'export/monday', ext: 'xlsx', scopes: BOARD_ONLY },
{ key: 'superproductivity', icon: 'fa-check-circle-o', label: 'Super Productivity', path: 'export/superproductivity', ext: 'json', scopes: BOARD_ONLY },
{ key: 'vikunja', icon: 'fa-file-archive-o', label: 'Vikunja', path: 'export/vikunja', ext: 'zip', scopes: BOARD_ONLY },
{ key: 'fizzy', icon: 'fa-file-archive-o', label: 'Fizzy', path: 'export/fizzy', ext: 'zip', scopes: BOARD_ONLY },
{ key: 'wrike', icon: 'fa-table', label: 'Wrike', path: 'export/wrike', ext: 'xlsx', scopes: BOARD_ONLY },
{ key: 'wrikeworkflow', icon: 'fa-sitemap', label: 'Wrike workflow', path: 'export/wrikeworkflow', ext: 'json', scopes: BOARD_ONLY },
{ key: 'teamwork', icon: 'fa-table', label: 'Teamwork.com', path: 'export/teamwork', ext: 'xlsx', scopes: BOARD_ONLY },
+3 -1
View File
@@ -55,7 +55,9 @@ export async function startCsvMapping(importTpl, { rows, excelBase64, uploadId,
}
const mapping = {
columns: { ...((preview.mapping && preview.mapping.columns) || {}) },
customFieldColumns: [],
// The guess ticks every column it has no field for, so nothing is left
// behind unless the user unticks it.
customFieldColumns: [...((preview.mapping && preview.mapping.customFieldColumns) || [])],
listName: TAPi18n.__('scrum-category-todo'),
};
importTpl.csvMappingState.set({
@@ -127,6 +127,10 @@ What the current code does (`parseAsana` in `models/lib/externalParsers.js`):
| `gid` | Source reference, for parent and dependency links |
| `name`, `notes` | Card title, description |
| `start_at` / `start_on`, `due_at` / `due_on` | Start date, due date |
| `actual_time_minutes` (time tracking) | Spent time (hours), written back on export |
| `html_notes`, when there are no `notes` | Card description, as text |
| `approval_status` of an approval task (not pending) | Label `approval:approved`, `approval:rejected` or `approval:changes requested` |
| `likes` of a comment story | The comment's 👍 reactions, by who liked it; likes the export does not name are counted in the loss report |
| `completed_at` (when completed) | End date |
| `created_at` | Creation date |
| `assignee` | Card member, when mapped |
@@ -110,7 +110,7 @@ The fetched JSON, which is also what the REST API takes:
| `created_at` | Created date |
| `completed` | Due date marked done; a completed to-do is archived |
| `assignees` | Members: the first as owner, then the others |
| Card `steps` (`title`, `completed`) | Checklist "Steps" |
| Card `steps` (`title`, `completed`, `due_on`, `assignees`) | Checklist "Steps", each item with the step's due date and first assignee |
| Comments (`content`, `creator`, `created_at`) | Comments |
| Card and to-do `id` | Source reference |
@@ -205,7 +205,7 @@ Last activity and Voting are not imported.
| Parent card | The card's parent, by title |
| Spent time, Overtime, Archived | Spent time, overtime, archived |
| `CustomField-...` | Board custom fields and the card's values |
| Other columns ticked in the mapping step | Text custom fields |
| Every other named column | A text custom field of its name: ticked in the mapping step by default, and always when no mapping is sent (a REST import) |
The export writes every column listed under **Export columns**.
@@ -213,8 +213,8 @@ The export writes every column listed under **Export columns**.
On import:
- columns no field uses and that were not ticked as custom fields,
including WeKan's Last activity and Voting columns;
- columns unticked in the mapping step, and WeKan's own Number, Last
activity and Voting columns, which no card field takes;
- members who were not mapped (Requested By and Assigned By keep them as
text);
- label names with spaces or commas in them: those separate two labels;
@@ -129,7 +129,8 @@ From the current code (`models/lib/clickupCsvFormat.js`):
Name, the board is named **Imported ClickUp tasks**.
The export writes the 31 workspace export columns, from **Task ID** to
**Rolled Up Time Text**, then **Checklist**:
**Rolled Up Time Text**, then **Checklist**, then one column per custom field
of the board that is not one of those named above:
- Task ID is the WeKan card id; Parent ID and Subtask IDs link the cards of
the same board;
@@ -162,6 +163,8 @@ The export writes the 31 workspace export columns, from **Task ID** to
| Due date | Due date |
| Start date | Start date |
| Time Spent / Time Tracked | Spent time, in hours |
| Task Link | `Source: <link>` at the end of the description |
| Any other column (a workspace export writes each custom field as one) | A custom field of the column's name |
| Priority | Custom field Priority |
| Task Type (other than task) | Custom field Task Type |
| Task Custom ID | Custom field Custom ID |
@@ -187,11 +190,11 @@ silently:
- a parent that is not in the same import, a Task ID used twice, and a parent
link that would form a cycle.
Other columns, such as Task Link, Rolled Up Time and the `Text` date columns,
are not read and not reported.
ClickUp's own Rolled Up Time and `Text` date columns repeat other columns,
and are not read.
The export leaves out comments, attachments, done state of checklist items,
spent time, archived cards, and custom fields other than those named above.
The export writes the spent hours as Time Spent (milliseconds). It leaves
out comments, attachments, done state of checklist items and archived cards.
## REST API
@@ -9,7 +9,9 @@ server its swimlane, and the messages the card's comments.
1. Export the channel with DiscordChatExporter in the **JSON** format.
2. In WeKan, go to **All Boards → New → Import → Discord (DiscordChatExporter)**.
3. Choose the `.json` file, or paste its text.
3. Choose the `.json` file, or paste its text - or, when DiscordChatExporter
ran with `--media` (the attachments downloaded beside the JSON), zip the
folder with the `.json` and its `_Files` folder and choose the `.zip`.
4. Map the authors to WeKan members, or leave them as they are.
5. Click **Import**.
@@ -49,9 +51,26 @@ replies are imported; pins, joins and other system messages are not.
Channel name and topic, category, server, messages with author, nickname and time.
## Replies
A reply, found by its `reference`, is a reply to the comment of the message it answers,
one level deep as WeKan's replies are: a reply to a reply goes under the same
comment. A reply to a message that is not in the file is a comment of its own,
starting with "↳".
## Reactions
A message's reactions become the comment's reactions, read from the emoji itself.
WeKan keeps a reaction by who reacted, so a reaction is kept for each person
mapped to a WeKan user in the members step. The loss report counts the
reactions of people who were not mapped, and those with an emoji WeKan cannot
store: a shortcode WeKan does not know, a server's or a chat's own emoji, or an
emoji of several code points (a skin tone, a flag). See
`models/lib/importedReactions.js`.
## What is not kept
Attachments and stickers (counted), embeds, reactions. What was left out is listed in the import's loss report, also in
Attachments that are only links (not downloaded with `--media`) and stickers (counted), embeds, a server's own emoji reactions. An attachment the zipped folder carries is an attachment of the channel's card. What was left out is listed in the import's loss report, also in
**Admin Panel → Problems → Recovery**.
## REST API
@@ -42,6 +42,7 @@ sources of the format.
| [Linear](./Linear/Linear.md) | Issues CSV export | Linear CSV |
| [Notion](./Notion/Notion.md) | *Markdown & CSV* export `.zip`, or one database CSV | Notion database CSV |
| [Redmine](./Redmine/Redmine.md) | Issues list *Also available in: CSV* | Redmine issues CSV |
| [Fizzy](./Fizzy/Fizzy.md) | Account export or personal data export `.zip`, or one card's `.json` | Fizzy account export `.zip` (its account import reads it) |
| [Plane](./Plane/Plane.md) | Workspace Settings → Exports `.zip` (CSV, JSON or XLSX inside), or one file from it | — (Plane has no file import) |
| [Taiga](./Taiga/Taiga.md) | Project export (dump) JSON | Taiga project dump JSON, with sprints |
| [Pivotal Tracker](./Pivotal-Tracker/Pivotal-Tracker.md) | Stories CSV | Pivotal Tracker CSV |
@@ -104,6 +105,7 @@ card, its messages the comments), and dated items in Calendar and Gantt.
| [Telegram](./Telegram/Telegram.md) | Telegram Desktop's JSON export `result.json` | — |
| [WhatsApp](./WhatsApp/WhatsApp.md) | *Export chat* `.txt` | — |
| [Discord (DiscordChatExporter)](./Discord/Discord.md) | DiscordChatExporter JSON | — |
| [Rocket.Chat](./Rocket-Chat/Rocket-Chat.md) | "Download my data" as JSON `.zip`, one room's `.json`, or a CSV importer `.zip` | Rocket.Chat CSV importer `.zip` |
| [Evernote (.enex)](./Evernote/Evernote.md) | Notes export `.enex` | Evernote (.enex) |
## WeKan's own formats and documents
@@ -155,8 +157,8 @@ never held whole in the browser or in the server's memory on the way:
that reason, and its partial file is removed;
- with no limit set, an import may be as large as the free disk space lets it
finish;
- a `.zip` export (Slack, Google Takeout, Vikunja, Notion, Plane) is opened from
the disk, its entries read as they are needed, and what they inflate to is
- a `.zip` export (Slack, Google Takeout, Vikunja, Notion, Plane, Rocket.Chat,
Fizzy) is opened from the disk, its entries read as they are needed, and what they inflate to is
counted against the limit or the free space; a mailbox is read a message at
a time, also inside a Takeout zip;
- JSON is built from the file a chunk at a time (`server/lib/streamJson.js`),
@@ -0,0 +1,119 @@
# Fizzy
WeKan imports a board from [Fizzy](https://github.com/basecamp/fizzy), the
kanban tool of 37signals, and exports a board as the account export Fizzy's own
account import reads.
## How to import
1. In Fizzy, export either:
- the whole account: **Account settings → Export** (admins and owners), or
- your own cards: your profile → **Download my data**.
Fizzy e-mails a link to the `.zip`.
2. In WeKan, go to **All Boards → New → Import → Fizzy**.
3. Choose the `.zip`, or one card's `.json` from the personal export, or paste
that file's text.
4. Map the people to WeKan members, or leave them as they are.
5. Click **Import**.
## How to import many boards at once
1. On the import page, choose **Fizzy**, then under **Import many boards**
choose several files.
2. Each file becomes its own board. The boards are imported without member
mapping; members can be mapped later.
Fizzy is imported through the generalized importer
(`models/kanboardCreator.js`), so the page also has the checkbox **One board
per project**: each Fizzy board becomes a WeKan board of its own.
From a script:
```bash
python3 api.py importboardsfrom fizzy FILE_OR_DIR ...
```
## How to export
1. Open the board, then **Board Settings → Export**, and choose **Fizzy**. The
board downloads as `<board>.zip`.
2. In Fizzy, make a new account from the zip with its account import
(**Import** when signing up an account, or `script/import-account` on a
server you run).
Each swimlane is a Fizzy board (a board with one swimlane is one Fizzy board
named after it), each list a column in the board's order, and the lists named
**Maybe?**, **Not now** and **Done** are Fizzy's own places of the same names.
An archived card is closed (Done). The account is named after the board. The
people are users of the new account with no e-mail address, so the import never
joins them to existing accounts; every user can open every board.
## How to export all boards at once
1. In WeKan, go to **All Boards**, open the sidebar and choose **Export all
boards**, then **Fizzy**.
2. One `.zip` downloads, with one Fizzy account export per board you can export.
From a script:
```bash
python3 api.py exportallboards fizzy boards.zip
```
## Format details
The account export (`app/models/account/data_transfer/*` in Fizzy) holds a row
of each table as `data/<table>/<id>.json` with every column of
`db/schema.rb`, `data/account.json`, the users as `data/users/<id>.json`, rich
text as `data/action_text_rich_texts/<id>.json` and the uploaded files as
`storage/<blob key>`. Ids are UUIDv7 written in base36, 25 characters. The
personal data export (`Card::Exportable`) holds `<number>.json` per card -
number, title, board, status, creator, description (HTML), dates and comments -
and its files under `<number>/<blob key>_<filename>`
(`models/lib/fizzyFormat.js`, `server/lib/fizzyArchive.js`).
A Fizzy board becomes a swimlane; its columns become lists in their position
order, after **Maybe?** (cards not yet triaged into a column) and before
**Not now** (postponed) and **Done** (closed) - the status names Fizzy itself
exports.
## What is kept
Boards, columns, cards with title, description, created date and due date,
tags as labels, assignees as the card's members, the creator as "requested by",
steps as the checklist **Steps**, comments by their author at their time, a
golden card as the colour gold, and the files in a description or a comment
(and a card's image) as attachments.
## What is not kept
Drafts never published (counted), reactions, watchers and pins (counted), and
boosts, events, notifications, webhooks and column colours. On export: users'
e-mail addresses, attachments, and a card's other dates. What was left out is
listed in the import's loss report, also in **Admin Panel → Problems →
Recovery**.
## REST API
- Import: `POST /api/boards/import/fizzy` with one card's `.json` text, or a
`.zip` as `{ "zipBase64": "..." }`.
- Export: `GET /api/boards/:boardId/export/fizzy`.
## How it is built and tested
`tests/fizzyFormat.test.cjs` reads an account export with columns out of
order, a triaged, an untriaged, a closed, a postponed and a draft card, tags,
assignments, steps, a comment, an embedded file and a missing one; reads a
personal data export with its files; refuses what is not a Fizzy export and a
file path outside a card's folder; and exports a board, checks every row has
every column Fizzy's import requires, is named by its id and names only users
of the export, and reads it back. The Playwright round trip
(`tests/playwright/specs/export-import-round-trip.e2e.js`) sends it through the
server.
## Sources
- [Fizzy source](https://github.com/basecamp/fizzy)
- [Fizzy account data transfer](https://github.com/basecamp/fizzy/tree/main/app/models/account/data_transfer)
- [Fizzy card export](https://github.com/basecamp/fizzy/blob/main/app/models/card/exportable.rb)
- [Fizzy exports API](https://github.com/basecamp/fizzy/blob/main/docs/api/sections/exports.md)
@@ -129,7 +129,9 @@ metadata and label colors are not imported.
The export (`forgejo` in `models/lib/externalExportFormatters.js`) is the same
as GitHub's: for each card that is not archived, `title`, `body`, `state`
(`closed` when the list name contains done, closed, complete, archiv or
finished, otherwise `open`), `labels` (as `{ "name": ... }`) and `due_date`.
finished, otherwise `open`), `labels` (as `{ "name": ... }`), `due_date`, the
owner as `assignee` (and `assignees`), the creator as `user`, `created_at`,
`closed_at` for a closed issue, and a **Time estimate (hours)** custom field as `time_estimate` (seconds).
## What is kept
@@ -142,6 +144,8 @@ finished, otherwise `open`), `labels` (as `{ "name": ... }`) and `due_date`.
| `state_reason` other than completed | Label `state_reason:...` |
| `milestone.title` | Label `milestone:...` |
| `milestone.due_on`, else `due_date` | Due date |
| `created_at`, and `closed_at` of a closed issue | Created and end dates |
| `time_estimate` (seconds, Gitea 1.23 and later) | Custom field **Time estimate (hours)** |
| First of `assignees` (`assignee`) | Owner, when mapped to a WeKan user |
| Other assignees | Labels `assignee:...` |
| `user.login` | Requested By |
@@ -67,6 +67,7 @@ page or a format in the export menu has no page here.
| [Linear](./Linear/Linear.md) | yes | yes |
| [Notion](./Notion/Notion.md) | yes | yes |
| [Redmine](./Redmine/Redmine.md) | yes | yes |
| [Fizzy](./Fizzy/Fizzy.md) | yes | yes |
| [Plane](./Plane/Plane.md) | yes | — |
| [Taiga](./Taiga/Taiga.md) | yes | yes |
| [Pivotal Tracker](./Pivotal-Tracker/Pivotal-Tracker.md) | yes | yes |
@@ -100,6 +101,7 @@ page or a format in the export menu has no page here.
| [Telegram](./Telegram/Telegram.md) | yes | — |
| [WhatsApp](./WhatsApp/WhatsApp.md) | yes | — |
| [Discord](./Discord/Discord.md) | yes | — |
| [Rocket.Chat](./Rocket-Chat/Rocket-Chat.md) | yes | yes |
| [Evernote](./Evernote/Evernote.md) | yes | yes |
The [overview](./External-Tools.md) groups them by kind.
@@ -149,7 +149,9 @@ creation or close dates, relationships or events.
The export (`models/lib/externalExportFormatters.js`, `githubLike`) writes, for
each card that is not archived: `title`, `body` (the description), `state`
(`closed` when the list name contains done, closed, complete, archiv or
finished, otherwise `open`), `labels` (as `{ "name": ... }`) and `due_date`.
finished, otherwise `open`), `labels` (as `{ "name": ... }`), `due_date`, the
owner as `assignee` (and `assignees`), the creator as `user`, `created_at`,
`closed_at` for a closed issue.
GitHub has no `due_date` field; WeKan reads it back when the file is imported
again.
@@ -164,6 +166,8 @@ again.
| `state_reason` other than completed | Label `state_reason:...` |
| `milestone.title` | Label `milestone:...` |
| `milestone.due_on`, else `due_date` | Due date |
| `created_at`, and `closed_at` of a closed issue | Created and end dates |
| `type.name` (GitHub's issue types: Bug, Feature, Task, or the organization's own) | Label `type:<name>` |
| First of `assignees` (`assignee`) | Owner, when mapped to a WeKan user |
| Other assignees | Labels `assignee:...` |
| `user.login` | Requested By |
@@ -167,8 +167,8 @@ each card that is not archived: `title`, `description`, `state` (`closed` when
the list name contains done, closed, complete, archiv or finished, otherwise
`opened`), `labels` (names), `due_date`, and, when the parts are ticked,
`assignees` (owner first), `author`, `created_at`, `closed_at` (closed items
only), comments as `notes`, and the sprint and release as `iteration` and
`milestone`. It writes no `iid`, so importing the file again does not add a
only), comments as `notes`, the spent hours as `time_stats.total_time_spent`
(seconds), and the sprint and release as `iteration` and `milestone`. It writes no `iid`, so importing the file again does not add a
second `Source:` line.
## What is kept
@@ -182,6 +182,8 @@ second `Source:` line.
| `milestone` | Scrum release, and label `milestone:...` |
| `iteration` | Scrum sprint, and label `iteration:...` |
| `issue_type` other than issue | Label `type:...` |
| `health_status` (on_track, needs_attention, at_risk) | Label `health:...` |
| `severity` of an incident (not UNKNOWN) | Label `severity:...` |
| `confidential` | Label `confidential`, and a warning |
| `due_date`, else `milestone.due_date` | Due date |
| `created_at` | Creation date |
@@ -129,7 +129,9 @@ metadata and label colors are not imported.
The export (`gitea` in `models/lib/externalExportFormatters.js`) is the same
as GitHub's: for each card that is not archived, `title`, `body`, `state`
(`closed` when the list name contains done, closed, complete, archiv or
finished, otherwise `open`), `labels` (as `{ "name": ... }`) and `due_date`.
finished, otherwise `open`), `labels` (as `{ "name": ... }`), `due_date`, the
owner as `assignee` (and `assignees`), the creator as `user`, `created_at`,
`closed_at` for a closed issue, and a **Time estimate (hours)** custom field as `time_estimate` (seconds).
## What is kept
@@ -142,6 +144,8 @@ finished, otherwise `open`), `labels` (as `{ "name": ... }`) and `due_date`.
| `state_reason` other than completed | Label `state_reason:...` |
| `milestone.title` | Label `milestone:...` |
| `milestone.due_on`, else `due_date` | Due date |
| `created_at`, and `closed_at` of a closed issue | Created and end dates |
| `time_estimate` (seconds, Gitea 1.23 and later) | Custom field **Time estimate (hours)** |
| First of `assignees` (`assignee`) | Owner, when mapped to a WeKan user |
| Other assignees | Labels `assignee:...` |
| `user.login` | Requested By |
@@ -90,7 +90,7 @@ The parser (`models/lib/googletasksApiFormat.js`):
| `due` | Due date |
| `status: completed` | Archived card |
| `completed` | End date |
| Subtasks (`parent`) | Checklist "Subtasks", done = completed |
| Subtasks (`parent`) | Checklist "Subtasks", done = completed, with the subtask's due date |
| `position` | Card and checklist item order |
| Hidden (cleared) completed tasks | Archived cards |
@@ -99,8 +99,8 @@ The parser (`models/lib/googletasksApiFormat.js`):
The import reports these on the loss report:
- deleted tasks (`deleted: true`), counted per list;
- the notes, due date and links of a subtask: a checklist item has only a
title and a done mark;
- the notes and links of a subtask: a checklist item has a title, done, a due
date and an assignee;
- a subtask whose parent is missing (it becomes its own card);
- a due date that is not a date;
- a second list with the same title (it is imported as `<title> (2)`);
@@ -94,7 +94,9 @@ What the current code does:
- `responsibleUserId` is the owner and `collaborators` are further
assignees, both by the user's full name (or e-mail without one), mapped to
WeKan members on the members step.
- `subTasks` become a checklist **Subtasks**, `finished` = done.
- `subTasks` become a checklist **Subtasks**, `finished` = done, a subtask's
`dueDate` the item's due date and its `userId` the item's assignee (when
mapped).
- Comments keep their author and date.
- The task id is the source reference.
- Limits: 20,000 tasks; comments are fetched for the first 5,000 tasks
@@ -117,7 +119,7 @@ What the current code does:
| `totalSecondsEstimate` | Custom field "Estimate (hours)" |
| `responsibleUserId` | Card member (owner) |
| `collaborators` | Card members |
| `subTasks` (`name`, `finished`) | Checklist "Subtasks" |
| `subTasks` (`name`, `finished`, `dueDate`, `userId`) | Checklist "Subtasks", with each item's due date and assignee |
| Comments | Comments, with author and date |
## What is not kept
@@ -126,7 +128,7 @@ The import reports these on the loss report:
- the column a due date is tied to (`targetColumnId`): WeKan keeps the date;
- every due date after the first;
- a subtask's own person and due date;
- a subtask due date that is not a date;
- a color that is not one of KanbanFlow's ten;
- a due date that is not a date;
- a task in a column the board does not have, and tasks that are not objects;
@@ -121,8 +121,9 @@ From the [format coverage](../Format-Coverage.md) audit:
creation dates, archive state, colors and source order are kept. Creation
dates survive the schema's `createdAt` autoValue through
`writeImportedEntity`. What has no equivalent is listed in the loss report:
file contents (the JSON carries attachment metadata only), time estimates,
external links, and task links WeKan cannot keep (see below).
file contents (the JSON carries attachment metadata only), a repeat other
than every 1 day, 7 days or 1 month, and task links WeKan cannot keep (see
below).
What the current code does (`parseKanboard` in
`models/lib/externalParsers.js`, `models/kanboardCreator.js`):
@@ -175,8 +176,12 @@ What the current code does (`parseKanboard` in
| `owner_username` (or `assignee_username`, `owner_id`, `owner_name`) | Card member, when mapped |
| `creator_username` (or `creator_name`) | Requested by |
| `tags`, category, `priority` | Board labels |
| `color_id` | Card color |
| `color_id` | Card color, written back on export |
| `time_spent` | Spent time (hours) |
| `time_estimated` | Custom field **Time estimate (hours)** |
| `score`, `reference` | Custom fields **Score** and **Reference** |
| `recurrence_status`, `recurrence_factor`, `recurrence_timeframe`: every 1 day, 7 days or 1 month | The card repeats daily, weekly or monthly |
| `external_links` (`url`, `title`) | A line each at the end of the description |
| `is_active` `0` | Archived card |
| `subtasks` (`title`, `status`) | Checklist **Subtasks** |
| `links` "is a child of" / "is a parent of" | The card's parent card |
@@ -189,7 +194,10 @@ each card: an `id` (1, 2, 3 ... in card order), `title`, `description`,
`column_name`, `swimlane_name`, `date_due`, `date_started`, `date_completed`,
`date_creation`, `owner_username`, `creator_username`, the labels as `tags`,
every checklist item as a `subtasks` entry (status `2` when finished, `0`
otherwise), the comments, and the card's parent and dependencies as `links`
otherwise), the comments, `time_spent`, a repeating open card's
`recurrence_status`, `recurrence_factor` and `recurrence_timeframe`, the
custom fields **Time estimate (hours)**, **Score** and **Reference** as
`time_estimated`, `score` and `reference`, and the card's parent and dependencies as `links`
in the `getAllTaskLinks` shape (`{ "id", "task_id", "label" }`, `task_id`
being the other task). Like Kanboard, each link is written from both tasks,
the second time with the opposite label, and the import folds the two back
@@ -200,10 +208,9 @@ when **Dependencies** is.
The import reports these on the loss report:
- `time_estimated` (WeKan cards have no estimate field; map it to a custom
field by hand);
- `files` (the API export carries metadata, not file contents);
- `external_links` (links to web pages and other systems are not imported);
- a repeat other than every 1 day, 7 days or 1 month (the task is imported
once);
- task links to a task that is not in the file;
- task links whose label is not one of Kanboard's built-in link types
(a link type added in Kanboard's settings);
@@ -93,6 +93,11 @@ What the current code does (`models/lib/leoOutline.js`):
- The outline is the `<v t="gnx">` nodes under `<vnodes>`. A node's body is
the `<t tx="gnx">` under `<tnodes>` with the same id. A node marked in Leo
carries `a="M"`.
- Leo stamps a node's id with the time it was made (`ekr.20260902080910.2`);
that time is the card's creation date. Leo writes it in local time with no
zone, so it is read as UTC.
- Any other attribute of a `<v>` or `<t>` is a Leo plugin's own data (its
"unknown attributes", pickled Python), and is reported.
- A level 3 node with children is a checklist named after it; all its
descendants, at any depth, are the items. Level 3 nodes without children
are the items of one checklist named after the card.
@@ -113,7 +118,8 @@ What the export writes (`models/lib/leoOutlineFormat.js`):
- each list as a top-level node, including lists without cards;
- each card as a child node, with its description as the body, marked when
its list's name looks finished (contains "done", "closed", "complete",
"archiv" or "finished");
"archiv" or "finished"), and its creation time in its id
(`wekan.YYYYMMDDHHMMSS.n`);
- each checklist as a child of the card, with its items as children, marked
when finished.
@@ -128,6 +134,7 @@ Archived cards and archived lists are not exported.
| Level 2 node: headline | Card title |
| Level 2 node: body | Card description |
| Level 2 node marked (`a="M"`) | Card with the label `done` |
| Level 2 node: the time in its id | Creation date |
| Level 3 node with children | Checklist, its descendants the items |
| Level 3 node without children | Item of a checklist named after the card |
| Marked item node | Finished checklist item |
@@ -137,10 +144,12 @@ Archived cards and archived lists are not exported.
The import reports these on the loss report:
- body text of a top-level (list) node: a WeKan list has no text field;
- a Leo plugin's data on a node (an attribute Leo itself does not write);
- nodes deeper than 64 levels.
The Leo export writes only lists, cards, descriptions, the done mark and
checklists. It does not write swimlanes, labels, dates, members, comments,
The Leo export writes only lists, cards, descriptions, the done mark, the
creation date and checklists. It does not write swimlanes, labels, other
dates, members, comments,
custom fields or attachments.
## REST API
@@ -97,10 +97,16 @@ What the import covers:
- `, `-separated labels;
- the created, started, completed (or canceled) and due dates;
- Archived as an archived card;
- Priority, Estimate, Project and Cycle (and Canceled) as custom fields.
- Priority, Estimate, Project and Cycle (and Canceled) as custom fields;
- with Scrum ticked in the import, each cycle as a Scrum sprint with its Cycle
Start and Cycle End, one per team (a cycle number is its team's), and each
project milestone as a Scrum release. The CSV gives a cycle no state: one
whose issues are all done is finished and not imported, as no commitment or
close snapshot is in the export, and any other is imported as planned. A
milestone has no dates in the CSV. Both are noted in the loss report.
Reported: Updated, Triaged, the cycle's dates, Initiatives, milestones, SLA
Status, dates that are not ISO 8601, and unknown priorities. The export writes
Reported: Updated, Triaged, Initiatives, SLA Status, dates that are not ISO
8601, and unknown priorities. The export writes
Linear's columns in its order, with the formula guard.
From the current code (`models/lib/linearCsvFormat.js`):
@@ -95,8 +95,14 @@ What the current code does (`parseMarkdownKanban` in
list called "Imported".
- A line starting with `- ` or `* `, with or without `[ ]`, `[x]` or `[X]`,
is a card. `[x]` adds the label `done`.
- A line that starts with white space, under a card, is added to that card's
description. Indented bullets therefore also become description lines.
- On a card line, `#tag` words are labels (a word that starts with a letter,
so `#1234` and `C#` stay in the title), and `@{2026-12-24}` with an optional
`@@{14:30}` (Obsidian Kanban), `📅 2026-12-24` (Obsidian Tasks) or
`due:2026-12-24` (todo.txt) is the due date. A due day that is no date is
reported.
- An indented `- [ ]` / `- [x]` line under a card is an item of its checklist.
Any other line that starts with white space is added to the card's
description; `\- [ ]` there is a description line, not an item.
- Other headings (`#`, `###` and deeper, or a second `#` line) are skipped.
Any other non-blank line is reported.
- Every card goes to the swimlane Default.
@@ -108,8 +114,12 @@ What the export writes (`formatMarkdownKanban` in
lists without cards are left out.
- Each card as `- [ ] <title>`, or `- [x] <title>` when its list's name looks
finished: it contains "done", "closed", "complete", "archiv" or
"finished" (case does not matter).
- Each non-blank line of the description, indented two spaces.
"finished" (case does not matter); then its labels as `#tags` (a space
written as `-`) and its due date as `@{day}`, with `@@{time}` when it has
one.
- Each non-blank line of the description, indented two spaces, a line that
looks like a checklist item escaped as `\- [ ]`.
- Each checklist item as an indented `- [ ]` / `- [x]` line.
- Archived cards and archived lists are not exported.
## What is kept
@@ -121,6 +131,9 @@ What the export writes (`formatMarkdownKanban` in
| `- [ ] Item`, `- Item`, `* Item` | Card |
| `- [x] Item` | Card with the label `done` |
| Indented lines under an item | Card description |
| `#tag` on an item | Label |
| `@{day}` `@@{time}`, `📅 day`, `due:day` | Due date |
| Indented `- [ ]` / `- [x]` under an item | Checklist item |
## What is not kept
@@ -129,10 +142,12 @@ heading, a card or an indented line under a card (for example a numbered list
item, or text before the first card). Headings other than the first `#` line
and the `##` lines are skipped.
The Markdown export writes only lists, card titles and descriptions. It does
not write swimlanes, labels (including `done`; the checkbox comes from the
list name), dates, members, comments, checklists, custom fields,
attachments, blank lines inside a description, or lists without cards.
The Markdown export writes lists, card titles, descriptions, labels, the due
date and checklist items. It does not write swimlanes, the `done` label (the
checkbox comes from the list name), a label that does not start with a
letter, other dates, members, comments, custom fields, attachments, blank
lines inside a description, or lists without cards. A card's checklists come
back as one checklist.
## REST API
@@ -66,9 +66,26 @@ messages**; a reply starts with `↳`.
Channels with header and purpose, posts and replies with author and time, teams.
## Replies
A reply, found by the post it is nested in, is a reply to the comment of the message it answers,
one level deep as WeKan's replies are: a reply to a reply goes under the same
comment. A reply to a message that is not in the file is a comment of its own,
starting with "↳".
## Reactions
A message's reactions become the comment's reactions, read from Mattermost's `emoji_name`, such as `+1` or `tada`.
WeKan keeps a reaction by who reacted, so a reaction is kept for each person
mapped to a WeKan user in the members step. The loss report counts the
reactions of people who were not mapped, and those with an emoji WeKan cannot
store: a shortcode WeKan does not know, a server's or a chat's own emoji, or an
emoji of several code points (a skin tone, a flag). See
`models/lib/importedReactions.js`.
## What is not kept
Attachments (counted), reactions, emoji, users' profiles and preferences. What was left out is listed in the import's loss report, also in
Attachments (counted), custom emoji, users' profiles and preferences. What was left out is listed in the import's loss report, also in
**Admin Panel → Problems → Recovery**.
## REST API
@@ -89,7 +89,10 @@ writes:
Columns are matched by name. The layout follows a real export: the test data
of the [plannr](https://github.com/program--/plannr) package, copied to
`tests/fixtures/planner/`.
`tests/fixtures/planner/`. The newer Planner's **Export as Excel** is described by
Microsoft's [Export a plan to Excel](https://support.microsoft.com/en-us/planner/export-a-plan-to-excel)
with Status, Task title and Assignments; those names are read as Progress,
Task Name and Assigned To.
What the import covers:
@@ -100,7 +100,8 @@ What the current code does (`parseNextcloudDeck` in
mark a card done with a timestamp). Either form, a date or Deck's REST API's
plain `true`, marks the card's due date done. A card without a due date has
no due date to mark, so `true` alone is not kept for it.
- Label colors are not read: labels are created black.
- A label keeps its color (Deck's hex `color`, such as `0082c9`); a label
without one is created black.
## What is kept
@@ -116,12 +117,13 @@ What the current code does (`parseNextcloudDeck` in
| `archived: true` | Archived card |
| `assignedUsers` | Card members, when mapped |
| `owner` | Requested by |
| `labels` (title) | Board labels |
| `labels` (`title`, `color`) | Board labels, with their colors |
| `comments` (`message`, `actorId`, `creationDateTime`) | Comments |
The export writes the board `title` and a stack per list, in order. Each card
has `title`, `description`, `duedate`, the labels as `{ title }`, `createdAt`,
the end date as `done`, the owner and further people as `assignedUsers`, the
the end date as `done` (or `done: true` for a due date ticked done without an
end date), the owner and further people as `assignedUsers`, the
creator as `owner` and the comments.
## Attachment files
@@ -118,7 +118,9 @@ them:
and a range `A → B`. WeKan also reads `YYYY-MM-DD`, `MM/DD/YYYY` and a
`(GMT+3)` style zone at the end. A time without a zone is taken as UTC.
- Checkboxes are `Yes` and `No`.
- Relations are the related page's title and its encoded path or URL.
- Relations are the related page's title and its encoded path or URL. A
related page that is one row of the export, in any of its databases, is a
"related to" dependency between the two cards.
- A row's page file starts with `# Title`, a blank line, one
`Property: value` line per non-empty property, a blank line, then the page
body.
@@ -262,7 +264,8 @@ The export writes, per card:
The import reports these on the loss report, rather than dropping them
silently:
- relation columns (links to other pages);
- a relation to a page that is not a row of the export, or to a title that
two rows share (it is not guessed which one);
- a **Last edited time** column;
- date columns after the ones above; they are kept as text fields, and the
report says which column was the due date;
@@ -97,7 +97,12 @@ What the import must cover:
- deeper outlines become checklists, with their descendants as items
(completed = finished);
- the head title becomes the board title;
- a list's note and `url` / `htmlUrl` / `xmlUrl` links are reported.
- on a card, OPML 2.0's `created` becomes the creation date and `category`
the labels, a `url` / `htmlUrl` / `xmlUrl` link goes at the end of the
description, and any other attribute (OmniOutliner writes its columns this
way) becomes a custom field;
- a list's note, and an attribute of a list or a checklist item, are
reported.
The export writes the same, with Workflowy's attribute names. Line breaks in
notes survive as `&#10;`. The file is parsed on the server only, and DTDs and
@@ -122,9 +127,10 @@ What the export writes (`models/lib/opmlOutlineFormat.js`):
- `<opml version="2.0">` with the board title in `<head><title>`;
- each list as a top-level `<outline text="…">`, including lists without
cards;
- each card as a child outline, with its description as `_note` and
- each card as a child outline, with its description as `_note`,
`_complete="true"` when its list's name looks finished (contains "done",
"closed", "complete", "archiv" or "finished");
"closed", "complete", "archiv" or "finished"), its creation date as
`created` (RFC 822) and its labels as `category`;
- each checklist as a child of the card, with its items as children,
`_complete="true"` when finished.
@@ -140,6 +146,10 @@ reader gives them back. Archived cards and archived lists are not exported.
| Level 2 outline: `text` (or `title`) | Card title |
| Level 2 outline: `_note` | Card description |
| Level 2 outline: `_complete` / `complete` = true | Card with the label `done` |
| Level 2 outline: `created` | Creation date |
| Level 2 outline: `category` (comma-separated, leading `/` taken off) | Labels |
| Level 2 outline: `url`, `htmlUrl`, `xmlUrl` | A link at the end of the description |
| Level 2 outline: any other attribute | Custom field of that name (a leading `_` taken off) |
| Level 3 outline with children | Checklist, its descendants the items |
| Level 3 outline without children | Item of a checklist named after the card |
| Completed item | Finished checklist item |
@@ -149,14 +159,17 @@ reader gives them back. Archived cards and archived lists are not exported.
The import reports these on the loss report:
- a `_note` on a top-level (list) outline;
- `url`, `htmlUrl` and `xmlUrl` attributes, on any outline;
- an attribute of a list or a checklist item other than its text and
complete state;
- a `created` that is not a date;
- outlines deeper than 64 levels.
Other attributes, such as `created`, are not read.
`type`, `isComment` and `isBreakpoint` only say how an outliner draws a row,
and are not read.
The OPML export writes only lists, cards, notes, the complete state and
checklists. It does not write swimlanes, labels, dates, members, comments,
custom fields or attachments.
The OPML export writes lists, cards, notes, the complete state, the creation
date, labels and checklists. It does not write swimlanes, other dates,
members, comments, custom fields or attachments.
## REST API
@@ -133,9 +133,11 @@ What the current code does (`parseOpenProject` in
(`_embedded.schemas`, or a work package's `_embedded.schema`); without a
schema the field keeps the name `customFieldN`. Values are read from the
work package (`raw` for formatted text) and from `_links` (the title).
- `estimatedTime` (ISO 8601 duration) becomes the custom field **Estimated
time (hours)**, and `percentageDone` the custom field **Progress (%)**.
`spentTime` becomes the card's spent hours.
- `estimatedTime` and `remainingTime` (ISO 8601 durations) become the custom
fields **Estimated time (hours)** and **Remaining time (hours)**, and
`percentageDone` the custom field **Progress (%)**. `spentTime` becomes the
card's spent hours, and the export writes a card's spent hours back as
`spentTime` (`PT1.5H`).
- Relations embedded on a work package are kept from their `from` side:
`blocks`, `blocked` (is blocked by), `duplicates`, `duplicated`; any other
type is kept as related-to.
@@ -161,7 +163,7 @@ What the current code does (`parseOpenProject` in
| Embedded `relations` | Dependencies |
| Embedded `watchers` | Card watchers, when mapped to a board member |
| Type, priority, category, version | Labels |
| `customFieldN`, `estimatedTime`, `percentageDone` | Custom fields |
| `customFieldN`, `estimatedTime`, `remainingTime`, `percentageDone` | Custom fields |
| `storyPoints` | Number field **Story points**, the Scrum estimate |
| `version`, `sprint`, `position` | Scrum release, sprint, backlog rank |
| Embedded comment activities | Comments |
@@ -3,8 +3,9 @@
WeKan imports and exports a board as an [Org mode](https://orgmode.org/manual/)
outline: the `.org` text file that Emacs, Orgzly, Beorg and organice write.
Top-level headings are lists and second-level headings are cards. TODO
keywords, priorities, tags, SCHEDULED, DEADLINE and CLOSED dates, the
`:CREATED:` property, body text and checkboxes are kept.
keywords, priorities, tags, SCHEDULED, DEADLINE and CLOSED dates and their
daily, weekly or monthly repeaters, properties, clocked time, body text and
checkboxes are kept.
## How to import
@@ -86,16 +87,21 @@ What the import must cover:
keyword as the `done` label);
- priorities become `priority:A` labels, and tags become labels;
- SCHEDULED / DEADLINE / CLOSED become the start, due and end dates;
- `:CREATED:` becomes the creation date;
- `:CREATED:` becomes the creation date, `:ID:` (or `:CUSTOM_ID:`) the card's
source reference, and every other property a custom field of that name;
- the closed `CLOCK:` lines of the `:LOGBOOK:` drawer add up to the spent
time;
- a `+1d`, `+1w` or `+1m` repeater (also `++` and `.+`) makes the card repeat
daily, weekly or monthly;
- body text becomes the description;
- checkboxes and level-3 headings without children become the card's
checklist, and level-3 headings with children become checklists of their
own;
- `#+TITLE` becomes the board title.
Timestamps have no zone in Org, and are read and written as UTC. Repeaters
and warning delays, text under a list heading and text before the first
heading are reported. Comments have no place in Org and are not exported.
Timestamps have no zone in Org, and are read and written as UTC. Other
repeaters and warning delays, other drawers, open clocks, text under a list
heading and text before the first heading are reported. Comments have no place in Org and are not exported.
What the current code does (`models/lib/orgModeFormat.js`):
@@ -107,8 +113,10 @@ What the current code does (`models/lib/orgModeFormat.js`):
- A planning line (SCHEDULED, DEADLINE, CLOSED) is read when it comes before
the body text. A timestamp may be active `<…>` or inactive `[…]`, with or
without a time.
- Of the property drawer, only `:CREATED:` is read. Other drawers (such as
`:LOGBOOK:`) are skipped.
- The property drawer is read whole: `:CREATED:`, `:ID:` / `:CUSTOM_ID:`, and
every other property as a custom field (a `:NAME+:` line appends to it). The
`:LOGBOOK:` drawer gives the spent time; its state-change notes are history
and are not kept. Any other drawer is reported.
- `- [ ]`, `+ [ ]` and numbered checkbox lines in the body become the first
checklist, named after the card, together with level-3 headings that have
no children. A level-3 heading with children is a checklist named after it,
@@ -129,7 +137,9 @@ What the export writes (`formatOrgMode` in the same module):
Org does not allow in a tag become `_`);
- `SCHEDULED:` (start date), `DEADLINE:` (due date) and, for a done card,
`CLOSED:` (end date);
- the creation date as `:CREATED:` in a property drawer;
- the creation date as `:CREATED:` and the custom fields as properties in a
property drawer (a space in a field name is written as `_`);
- a repeating card's repeater on its DEADLINE (`+1d`, `+1w`, `+1m`);
- the description, indented three spaces;
- each checklist as `*** <checklist>` with `**** TODO` / `**** DONE` items.
@@ -149,6 +159,10 @@ Archived cards and archived lists are not exported.
| DEADLINE | Due date |
| CLOSED | End date |
| `:CREATED:` property | Creation date |
| `:ID:` / `:CUSTOM_ID:` property | Source reference |
| Any other property | Custom field |
| `CLOCK:` lines in `:LOGBOOK:` | Spent time |
| `+1d` / `+1w` / `+1m` repeater | Daily / weekly / monthly recurrence |
| Body text | Card description |
| `- [ ]` / `- [X]` checkboxes, level-3 headings without children | Checklist named after the card |
| Level-3 heading with children | Checklist, its descendants the items |
@@ -159,14 +173,14 @@ The import reports these on the loss report:
- text before the first heading (other than `#+` lines);
- text under a level-1 (list) heading;
- a repeater (`+1w`) or warning delay (`-2d`) on a planning timestamp: the
date is kept, the repeat is not;
- a SCHEDULED, DEADLINE or CLOSED value that is not a date.
- a repeater other than every 1 day, week or month (`+2w`), or a warning
delay (`-2d`): the date is kept, the repeat is not;
- a SCHEDULED, DEADLINE or CLOSED value that is not a date, and a `:CREATED:`
that is not one;
- a property line that is not `:NAME: value`, an open clock (no end), and any
drawer other than PROPERTIES and LOGBOOK.
Properties other than `:CREATED:` and other drawers are skipped without a
report.
The Org mode export does not write swimlanes, members, comments, custom fields
The Org mode export does not write swimlanes, members, comments, spent time
or attachments.
## REST API
@@ -89,6 +89,8 @@ Limit: 20,000 cards. Every card goes to the swimlane Default.
| Planka | WeKan |
| --- | --- |
| Board `name` | Board title |
| v2 `customFieldValues` (`content`), named by `customFields` and `customFieldGroups` | Custom fields of the field's name (`Group: Field` when two groups have a field of that name) |
| Card `stopwatch.total` (seconds) | Spent time (hours) |
| Lists (`active`, `closed`) | Lists, in order |
| Card `name` | Card title |
| `description` | Card description |
@@ -108,8 +110,7 @@ The import reports these on the loss report:
- cards in the Planka trash;
- attachments: they are files on the Planka server;
- custom field values;
- the stopwatch time;
- a custom field value of a field the export does not name;
- a due date that is not a date;
- a second list with the same name (it is imported as `<name> (2)`);
- a card whose list is not on the board;
@@ -0,0 +1,110 @@
# Rocket.Chat
WeKan imports a Rocket.Chat export as a board for **Board View → Chat**, and
exports a board as the `.zip` Rocket.Chat's own CSV importer reads. A room is a
card and its messages are the card's comments.
## How to import
1. In Rocket.Chat, open your avatar → **Account → Preferences → My Data**, and
choose **Export my data** with **Export as JSON**. Rocket.Chat e-mails a link
to the `.zip`. (One room: the room's kebab menu → **Export messages** as a
file in JSON gives that room's `.json`.)
2. In WeKan, go to **All Boards → New → Import → Rocket.Chat**.
3. Choose the `.zip`, or one room's `.json`, or paste that file's text. The
`.zip` Rocket.Chat's CSV importer reads (as WeKan exports it) is read too.
4. Map the authors to WeKan members, or leave them as they are.
5. Click **Import**.
## How to import many boards at once
1. On the import page, choose **Rocket.Chat**, then under **Import many boards**
choose several files.
2. Each file becomes its own board. The boards are imported without member
mapping; members can be mapped later.
Rocket.Chat is imported through the generalized importer
(`models/kanboardCreator.js`), so the page also has the checkbox **One board
per project**: each swimlane the import would create becomes its own board.
From a script:
```bash
python3 api.py importboardsfrom rocketchat FILE_OR_DIR ...
```
## How to export
1. Open the board, then **Board Settings → Export**, and choose
**Rocket.Chat**. The board downloads as `<board>.zip`.
2. In Rocket.Chat, go to **Administration → Workspace → Import → Import new
file**, choose **CSV**, and upload the `.zip`.
The zip holds `users.csv`, `channels.csv` and a `<channel>/messages.csv` per
card. A card is a public channel, named in the letters Rocket.Chat accepts by
default (`[0-9a-zA-Z-_.]`), and its description and comments are the channel's
messages, by their author at their time. Each author is a user with the address
`<username>@wekan.invalid`, so the import never joins them to existing accounts
by e-mail.
## How to export all boards at once
1. In WeKan, go to **All Boards**, open the sidebar and choose **Export all
boards**, then **Rocket.Chat**.
2. One `.zip` downloads, with one Rocket.Chat `.zip` per board you can export.
From a script:
```bash
python3 api.py exportallboards rocketchat boards.zip
```
## Format details
"Download my data" as JSON (`apps/meteor/server/lib/dataExport`):
`channels.json` has a `{ roomId, roomName, type }` line per room, and each room's
`<roomName>.json` beside it has a `{ msg, username, ts, attachments, type }` line
per message; the uploaded files are under `assets/<fileId>-<fileName>`. The CSV
importer's zip (`apps/meteor/server/lib/import/csv/CsvImporter.ts`) has no header
rows: `users.csv` is `username, email, name`, `channels.csv` is
`name, creator, public | private, members a;b`, a channel's folder holds
`username, ts (milliseconds), text`, and `directmessages/` holds
`username, other username, ts, text` (`models/lib/chatExportFormats.js`,
`server/lib/chatArchives.js`).
Rooms become cards: public channels in the list **Channels**, private groups in
**Groups**, direct messages in **Direct messages** (named by their people) and
omnichannel rooms in **Omnichannel**, all in the swimlane **Rocket.Chat**.
## What is kept
Rooms and their kind, messages with author, the user's name from `users.csv`,
and time; the files a message carries when the zip holds them, as the card's
attachments.
## What is not kept
System messages (joins, leaves, topic changes - counted), files the zip does not
hold (counted), threads and reactions, which the export does not write. On
export: a card's list, labels, checklists and attachments, which the CSV
importer has no place for. What was left out is listed in the import's loss
report, also in **Admin Panel → Problems → Recovery**.
## REST API
- Import: `POST /api/boards/import/rocketchat` with one room's `.json` text, or
a `.zip` as `{ "zipBase64": "..." }`.
- Export: `GET /api/boards/:boardId/export/rocketchat`.
## How it is built and tested
`tests/chatExportFormats.test.cjs` reads a "Download my data" zip with a
public, a private and a direct room, a system message and an attached file,
reads the CSV importer's zip with quoted multi-line messages and direct
messages, refuses what is not a Rocket.Chat export, and exports a board and
reads it back - with no header rows and no path outside a channel folder.
## Sources
- [Rocket.Chat data export source](https://github.com/RocketChat/Rocket.Chat/tree/develop/apps/meteor/server/lib/dataExport)
- [Rocket.Chat CSV importer source](https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/server/lib/import/csv/CsvImporter.ts)
@@ -10,7 +10,10 @@ card's comments, by their author and time.
Export**, start the export and download the `.zip` when Slack mails the
link.
2. In WeKan, go to **All Boards → New → Import → Slack**.
3. Choose the `.zip` file.
3. Choose the `.zip` file. To bring the messages' files along, give a Slack
token with the `files:read` scope under the file sign-in (a user token of a
Slack app installed in the workspace): the files are on Slack's file host,
behind its sign-in, and are not in the export zip.
4. Map the Slack users to WeKan members, or leave them as they are.
5. Click **Import**, and open the board in **Board View → Chat**.
@@ -54,9 +57,26 @@ out.
Channels with their topic and purpose, every message and thread reply with its author and time.
## Replies
A reply, found by its `thread_ts`, is a reply to the comment of the message it answers,
one level deep as WeKan's replies are: a reply to a reply goes under the same
comment. A reply to a message that is not in the file is a comment of its own,
starting with "↳".
## Reactions
A message's reactions become the comment's reactions, read from Slack's shortcode, such as `thumbsup` or `tada`.
WeKan keeps a reaction by who reacted, so a reaction is kept for each person
mapped to a WeKan user in the members step. The loss report counts the
reactions of people who were not mapped, and those with an emoji WeKan cannot
store: a shortcode WeKan does not know, a server's or a chat's own emoji, or an
emoji of several code points (a skin tone, a flag). See
`models/lib/importedReactions.js`.
## What is not kept
Files and images (counted in the loss report), reactions, edits and pins. The zip is read within the same bounds as the other zip imports. What was left out is listed in the import's loss report, also in
Files and images without a token, deleted ones, and ones hidden by the plan's history limit (counted in the loss report), edits and pins. With a token, each file is downloaded from `files.slack.com` only, through the import's guarded download, and attached to the channel's card. The zip is read within the same bounds as the other zip imports. What was left out is listed in the import's loss report, also in
**Admin Panel → Problems → Recovery**.
## REST API
@@ -179,7 +179,8 @@ The export writes a backup Super Productivity's **Import from File** reads:
The import reports these on the loss report, rather than dropping them
silently:
- repeat configurations (the task imports once);
- a repeat configuration other than every 1 day, week or month, or a paused
one (the task imports once);
- reminders;
- a task's link to an issue of an issue provider;
- project notes;
@@ -243,3 +244,14 @@ The HTTP routes:
See also the [format coverage table](../Format-Coverage.md) and
[all formats](../External-Tools.md).
## Repeating tasks
A task's repeat configuration (`taskRepeatCfg`) that repeats every 1 day,
week or month makes the card repeat daily, weekly or monthly. The export
writes an open repeating card's repeat back as a `taskRepeatCfg` with the
fields and defaults of Super Productivity's own model
(`src/app/features/task-repeat-cfg/task-repeat-cfg.model.ts`): the cycle, its
quick setting, the start date (the due date, or the creation date), the
weekday of a weekly repeat, and today as the last creation day, since the card
is this period's task.
@@ -144,9 +144,10 @@ python3 api.py exportallboards taiga boards.zip
the board's Scrum estimate, in points.
- **Tags**: `tags_colors` give each label the nearest WeKan label color.
Older Taiga versions stored a tag as `[name, color]`; that color is used too.
- **Blocked** (with the blocked note), **Client requirement**, **Team
requirement**, **Due date reason** and **Iocaine** become custom fields of
those names.
- **Blocked**, with the blocked note as its reason, is the card's Blocked
flow field, and the imported board shows it (Board Settings / Card).
**Client requirement**, **Team requirement**, **Due date reason** and
**Iocaine** become custom fields of those names.
People become card members, assignees and watchers only when they are mapped
to WeKan users. The import page imports Taiga without member mapping, so
@@ -197,8 +198,10 @@ The export writes a dump with every key Taiga's exporter writes, in its order:
- Comments become history entries.
- Custom fields become custom attributes, typed number, checkbox or text.
- **Story points** become role points of one role, **Team**. The fields
Task status, Blocked, Client requirement, Team requirement, Due date reason
and Iocaine go back to Taiga's own fields.
Task status, Client requirement, Team requirement, Due date reason and
Iocaine go back to Taiga's own fields, and the card's Blocked flow field (or
a Blocked custom field of a board imported before) to `is_blocked` and
`blocked_note`.
- Scrum sprints with both a planned start and end become milestones. A closed
sprint is a closed milestone. A cancelled sprint is left out. A card's sprint
is its story's, task's or issue's milestone, and its backlog rank is the
@@ -232,7 +235,7 @@ The export writes a dump with every key Taiga's exporter writes, in its order:
| Issue | Card in the Issues swimlane, list per issue status |
| Issue type, priority, severity | `type:`, `priority:`, `severity:` labels |
| `generated_from_issue`, `generated_from_task` | Related link |
| `is_blocked`, `blocked_note` | Blocked custom field |
| `is_blocked`, `blocked_note` | The card's Blocked flow field, with its reason |
| `client_requirement`, `team_requirement` | Client requirement, Team requirement custom fields |
| `due_date_reason` | Due date reason custom field |
| `is_iocaine` | Iocaine custom field |
@@ -9,7 +9,9 @@ Chat**: each chat is a card and its messages are the card's comments.
(or a chat's menu → **Export chat history**), choose the format
**Machine-readable JSON**, and export.
2. In WeKan, go to **All Boards → New → Import → Telegram**.
3. Choose `result.json`, or paste its text.
3. Choose `result.json`, or paste its text - or, to bring the photos and
files along, zip the whole export folder (the one with `result.json`,
`photos/` and `files/`) and choose the `.zip`.
4. Map the people to WeKan members, or leave them as they are.
5. Click **Import**.
@@ -52,9 +54,26 @@ out.
Chats, message text, author and time.
## Replies
A reply, found by its `reply_to_message_id`, is a reply to the comment of the message it answers,
one level deep as WeKan's replies are: a reply to a reply goes under the same
comment. A reply to a message that is not in the file is a comment of its own,
starting with "↳".
## Reactions
A message's reactions become the comment's reactions, read from the emoji itself; Telegram's export names the most recent people who reacted.
WeKan keeps a reaction by who reacted, so a reaction is kept for each person
mapped to a WeKan user in the members step. The loss report counts the
reactions of people who were not mapped, and those with an emoji WeKan cannot
store: a shortcode WeKan does not know, a server's or a chat's own emoji, or an
emoji of several code points (a skin tone, a flag). See
`models/lib/importedReactions.js`.
## What is not kept
Photos, files, stickers and voice messages (counted), reactions, edits, replies as links. What was left out is listed in the import's loss report, also in
Photos and files the export did not download ("File not included"), and every one when only `result.json` is imported (counted); stickers and voice messages not in the zipped folder (counted); custom emoji reactions; edits. A photo or file the zipped folder carries is an attachment of the chat's card. What was left out is listed in the import's loss report, also in
**Admin Panel → Problems → Recovery**.
## REST API
@@ -149,16 +149,18 @@ What the current code does:
| WeKan export | WeKan |
| --- | --- |
| Board fields, labels, members, settings | The board, its labels and members (mapped or placeholder users) |
| `swimlanes`, `lists` | Swimlanes and lists, with order, archive and color |
| `cards` | Cards with text, order, archive, dates, people, labels, custom fields, votes, poker, locations and dependencies |
| `customFields` | Custom fields |
| `checklists`, `checklistItems` | Checklists and items |
| Board fields, labels, members | The board, its labels and members (mapped or placeholder users) |
| Board Settings | Every one: what a card and a minicard show and in which order, the flow policies, the board views, column sets, WIP limit groups, date format, notification delivery, announcement (`models/lib/wekanBoardFields.js`) |
| `swimlanes`, `lists` | Swimlanes and lists, with order, archive and color; a swimlane's height; a list's WIP limit, flow policy, split into Doing and Done, and its role restrictions |
| `cards` | Cards with text, order, archive, dates and the due date's done tick, people, labels, custom fields, flow fields (Blocked, Class of service, MoSCoW, WSJF), votes and poker by who voted, stickers, locations, drawings, column-set columns, kind, map position, mail headers, recurrence, display settings and dependencies (`models/lib/wekanCardFields.js`) |
| `customFields` | Custom fields, with "admin only", "read only", the card kinds they apply to and the list sum |
| `checklists`, `checklistItems` | Checklists, with their hide settings and reset schedule (counted from the import), and items with their assignee |
| `subtaskItems`, parent links | Subtasks |
| `comments` | Comments |
| `comments` | Comments, a reply under the comment it answers |
| `activities` | Activities |
| `rules`, `triggers`, `actions` | Rules |
| `attachments` (base64 in JSON, files in .zip) | Attachments, in the default storage |
| `attachments` (base64 in JSON, files in .zip) | Attachments, in the default storage. The original is the file; a thumbnail is made from it when it is first shown, so it is not exported |
| `type`: a template board, card, list or swimlane | It stays a template. A user's own Templates board comes as a template board (the importing user's own Templates board stays theirs), and is noted in the loss report |
| Scrum records | Sprints, releases and Scrum settings |
| Board background attachments | Board background |
@@ -169,7 +171,22 @@ What the current code does:
- Parts not ticked under **Select what to include:** are left out of the
export, or out of the import.
- Ids are kept only as source references: the imported board, its cards and
everything else get new ids.
everything else get new ids. A user in a vote, a poker card or "blocked by"
is the mapped user; one who is not on the new board is left out.
- What a file must not decide on its own is left to the new board's admin:
who may open or edit the board (organizations, teams, email domains, "every
signed-in user may edit"), whether the board accepts inbound email, and a
list role exception that lets a role do more than the board's rule (one that
lets it do less is kept).
- What belongs to the exporting WeKan: the trash, external sync bookkeeping,
running Pomodoro and flow timers, linked cards and Gantt links to other
boards, and default boards for subtasks and dates. The two lists, with the
reason for each field, are `NOT_COPIED` in `models/lib/wekanBoardFields.js`
and `models/lib/wekanCardFields.js`, and `notCopied` in
`models/lib/wekanRecordFields.js` for the rest; `tests/wekanCardFields.test.cjs` fails
when a field of the schema is in neither.
- A Board Settings value this WeKan's schema refuses - from an older or newer
WeKan - is left at its default and listed in the import's loss report.
Older WeKan versions used other database schemas. For moving data from them,
see [Migrating from old WeKan manually](./Migrating-from-old-Wekan-manually.md)
@@ -82,3 +82,75 @@ release still appeared successful.
Keeping synchronization in a required reusable workflow gives it one clear
result per repository and avoids attempting the same source update from
architecture-specific snap jobs.
## How the three snaps reach every Snap Store channel
`wekan`, `wekan-ondra` and `wekan-gantt-gpl` are the same program under three
snap names. One run of `release-all.yml` makes all three:
| Job | Snaps | Architectures |
| --- | --- | --- |
| `snap-native` | `wekan` | amd64, arm64 |
| `snap-launchpad` | `wekan` | armhf, ppc64el, s390x, riscv64 |
| `snap-variants` | `wekan-ondra`, `wekan-gantt-gpl` | amd64, arm64 |
Each job uploads its snap with `--release` to stable, candidate, beta and edge,
and attaches it to the GitHub Release. Until v13.21 `snap-variants` did not
attach its snaps, so older releases carry only `wekan_*.snap`.
The Snap Store can keep an upload "processing" for hours and then not release
it: on v13.20 every snap job was green and the store kept the old version. So
the last snap job of the release, `snap-store`, calls
`.github/workflows/snap-store.yml` ("Push Snap to Store") for the release tag.
For every snap on the release it runs `releases/snap-store-push.sh`, which
releases a revision the store already has by number, uploads one it has not,
uploads again after a store-side failure ("Error checking upload
uniqueness", HTTP 5xx), waits for one still processing, and is red when a snap
did not reach its channels. "Push Snap to Store" also runs by hand from the
Actions tab, for any release tag.
`release-all-missing.yml` finishes a release that lacks snaps:
- the `wekan` snaps come from retrying the release's own `snap-native` or
`snap-launchpad` job (its `recover` job);
- a missing `wekan-ondra` or `wekan-gantt-gpl` snap is made from the release's
`wekan` snap of the same architecture by `releases/snap-rename.sh`, which
changes only `name:` and `title:` in `meta/snap.yaml` - what `snap-variants`
changes in `snapcraft.yaml` - and attaches it;
- then it calls "Push Snap to Store" for that release.
Run with no version, it checks the newest releases
(`releases/release-missing-scan.sh`, the `scan` input says how many) and starts
itself once for each release that is missing something.
## When the Snap Store holds a revision for review
The store can keep an uploaded revision in its manual review queue. On the
snap's dashboard (`https://dashboard.snapcraft.io/snaps/<name>/`, Releases)
it is listed under "Revisions available to release" as **Can't be released:
ReviewQueued**. That happened to `wekan` (revision 4793) and `wekan-gantt-gpl`
(revision 913) on v13.21, while `wekan-ondra`, built from the same tag with
only its name changed, was released.
While a revision is held:
- uploading the same file again answers "Error checking upload uniqueness":
the store takes a file only once. "Push Snap to Store" therefore asks the
store first (`snapcraft revisions`; snapcraft 9 renamed `list-revisions`,
whose failure made v13.20 and v13.21 upload again and again), releases a
revision it already has, uploads a file at most once, and after the
uniqueness answer releases the store's revision or says it is held;
- every release goes to each channel on its own (stable, candidate, beta,
edge), so a channel the store refuses does not keep the revision out of the
others, and each refusal is an error line in the build log; the workflow
also releases the newest revision of every architecture the store has
(`releases/snap-store-release-newest.sh`), whatever the GitHub release
holds;
- no upload or release command can skip the review. Ask for it at
<https://forum.snapcraft.io/c/store-requests/>, naming the snap and the
revision, then run "Push Snap to Store" again: it releases the reviewed
revision to every channel.
"Push Snap to Store" also makes a missing `wekan-ondra` or `wekan-gantt-gpl`
snap from the release's `wekan` snaps (`releases/snap-rename.sh`), so a
release cut before the variants were attached can still be pushed.
@@ -10,7 +10,7 @@ This is without container (without Docker or Snap).
Right click and download files 1-4:
1. [wekan-13.21-win64.zip](https://github.com/wekan/wekan/releases/download/v13.21/wekan-13.21-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
1. [wekan-13.22-win64.zip](https://github.com/wekan/wekan/releases/download/v13.22/wekan-13.22-win64.zip) or newest available at https://github.com/wekan/wekan/releases/
2. [node.exe](https://nodejs.org/dist/latest-v26.x/win-x64/node.exe)
@@ -22,7 +22,7 @@ Right click and download files 1-4:
6. Double click `mongodb-windows-x86_64-7.0.34-signed.msi` . In installer, uncheck downloading MongoDB compass.
7. Unzip `wekan-13.21-win64.zip` , inside it is directory `bundle`, to it copy other files:
7. Unzip `wekan-13.22-win64.zip` , inside it is directory `bundle`, to it copy other files:
```
bundle (directory)
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Bak Redmine, buka Issues proyek, pileh Also available in: CSV bak bagian bawah dapeuta, pileh kolom (All columns, ngon Description) ngon ekspor, lheuh nyan tempel CSV. Redmine geubri nan kolom lam bahsa droeneueh, nyan pasai atô bahsa droeneueh u bahsa Inggreh bak My account sigohlom ekspor. Tiep status jeuet keu dapeuta ngon isu jeuet keu kad, ngon tracker sibagoe label, ureueng geutugaih, ureueng tuléh, tanggal, tugaih induk ngon isu meuhubong; prioritas, kategori, versi tujuan, watèe peukira, % Done ngon ruang khusus jeuet keu ruang khusus.",
"import-board-instruction-notion": "Bak Notion, buka database sibagoe on peunoh, pileh ••• ngon Export, pileh Markdown & CSV, ngon pileh file .zip nyang geuunduh, atawa saboh CSV database nibak nyan, atawa tempel CSV nyan. Kolom ngon nan Status jeuet keu dapeuta (meunyoe hana, kolom phon nyang lagee pileh jeuet keu dapeuta, ngon laporan impor geupeugah kolom pat); baréh jeuet keu kad ngon judul, tag sibagoe label, ureueng sibagoe anggota, tanggal, ngon teks on sibagoe deskripsi; kolom laen jeuet keu ruang khusus. Hubongan, gamba ngon lampiran h'an geuimpor.",
"import-board-instruction-plane": "Bak Plane, buka Workspace Settings, pileh Exports, ekspor proyek sibagoe JSON, CSV atawa Excel ngon unduh file .zip, lheuh nyan pileh file nyan, atawa saboh file nibak dalam jih, atawa tempel JSON atawa CSV. Keuadaan jeuet keu dapeuta, proyek jeuet keu jalur, ngon isu jeuet keu kad ngon tanda, induk, ureueng geutugaih, label, tanggal, link ngon komen jih; prioritas, peukira, siklus ngon modul jeuet keu ruang khusus. Ekspor Plane hana deskripsi atawa lampiran, nyan pasai h'an geuimpor.",
"import-board-instruction-fizzy": "Bak Fizzy, ekspor akun bak \"Account settings\", atawa kad droeneuh mandiri ngon \"Download my data\", lheuh nyan pilèh fail .zip nyang geukirim lé Fizzy keu droeneuh, atawa fail .json saboh kad. Panel jeuet keu swimlane ngon kolom jeuet keu dapeuta, ngon \"Maybe?\", \"Not now\" ngon \"Done\" lagée bak Fizzy; kad teutap na deskripsi, label, ureueng geutugaih, langkah sibagoe dapeuta peureksa, komen ngon fail jih.",
"import-board-instruction-mail": "Pilèh fail .mbox, lagèe nyang geukeubah lé Thunderbird, Apple Mail, mutt atawa Gmail meulalui Google Takeout, atawa saboh pesan .eml, atawa tamp teks jih. Tiep-tiep haba jeuet keu saboh kad lam dapeuta Inbox, ngon peukirém, peuneurimong ngon pokok haba jih, mangat jeuet deuh lam ngon Email; balasan jeuet keu komen jih. Label Gmail jeuet keu label. Lampiran hana geuimpor.",
"import-board-instruction-ical": "Pilèh fail almanak .ics, lagèe nyang geu-ekspor lé Google Calendar, Apple Calendar atawa Reminders, Thunderbird, Nextcloud atawa Outlook, atawa tamp teks jih. Tugaih jak u To Do, In Progress, Done atawa Cancelled meunurôt status jih, ngon acara u Events, ngon tanggai phôn ngon bataih watèë jih, mangat deuh lam ngon Calendar ngon Gantt. Kategori ngon prioritas jeuet keu label. Item nyang meuulang geuimpor sigoe mantong.",
"import-board-instruction-googletakeout": "Bak takeout.google.com, pilèh Tasks, Keep, Mail, Calendar ngon Google Chat, peugöt ekspor ngon unduh fail .zip, lheueh nyan pilèh fail nyan sinoe. Tiep-tiep produk jeuet keu saboh swimlane: surat keu ngon Email, dapeuta tugaih ngon cataan ngon dapeuta peureksa jih, acara almanak ngon tugaih ngon tanggai, ngon ruang chat nyang pesan jih jeuet keu komen keu ngon Chat. Produk laén ngon lampiran hana geuimpor.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Lam Telegram Desktop, buka Settings, Advanced, Export Telegram data, pilèh format JSON ngon ekspor, lheueh nyan pilèh fail result.json, atawa tamp teks jih. Tiep-tiep chat jeuet keu saboh kad lam Direct messages, Groups atawa Channels, ngon pesan jih jeuet keu komen kad, mangat ngon Chat peudeuh chat nyan. Foto ngon fail hana geuimpor.",
"import-board-instruction-whatsapp": "Lam WhatsApp, buka chat, pilèh Export chat hana media, ngon pilèh fail .txt sinoe, atawa tamp teks jih. Chat nyan jeuet keu saboh kad nyang pesan jih jeuet keu komen, meunurôt peukirém ngon watèë jih, mangat ngon Chat peudeuh chat nyan. Media ngon pesan sistem hana geuimpor.",
"import-board-instruction-discord": "Ekspor saboh saluran Discord ngon DiscordChatExporter lam format JSON ngon pilèh fail .json, atawa tamp teks jih. Saluran nyan jeuet keu saboh kad lam kategori jih, ngon pesan jih jeuet keu komen kad, mangat ngon Chat peudeuh saluran nyan. Server jeuet keu swimlane. Lampiran hana geuimpor.",
"import-board-instruction-rocketchat": "Bak Rocket.Chat, ekspor data droeneuh sibagoe JSON bak \"My Data\" ngon pilèh fail .zip nyang geukirim keu droeneuh, atawa fail .json nyang geuekspor nibak saboh ruang. Tiep-tiep ruang jeuet keu saboh kad ngon pesan jih jeuet keu komen kad, mangat ngon Chat peudeuh ruang nyan. Fail .zip nyang geuekspor lé WeKan keu pengimpor CSV Rocket.Chat geubaca cit.",
"import-board-instruction-evernote": "Lam Evernote, ekspor cataan atawa saboh buku cataan sibagoe fail .enex ngon pilèh fail nyan sinoe, atawa tamp teks jih. Tiep-tiep cataan jeuet keu saboh kad ngon teks jih, kotak to-do jih sibagoe dapeuta peureksa, tag jih sibagoe label ngon peuingat jih sibagoe bataih watèë; cataan nyang peuingat jih ka seuleusoe jak u Done. Gamba ngon fail lampiran hana geuimpor.",
"tool-group-kanban": "Alat Kanban ngon proyek",
"tool-group-issues": "Pelacak masalah ngon kontrol versi",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Maak in Redmine die projek se Issues oop, kies Also available in: CSV onderaan die lys, kies die kolomme (All columns, met Description) en voer dit uit; plak dan die CSV. Redmine benoem die kolomme in jou taal, dus moet jy voor uitvoer jou taal in My account na English verander. Elke status word ’n lys en werkitems word kaarte, met die werkitemtipe as ’n etiket, toegewysde persoon, outeur, datums, ouertaak en verwante werkitems; prioriteit, kategorie, teikenweergawe, beraamde tyd, % Done en pasgemaakte velde word pasgemaakte velde.",
"import-board-instruction-notion": "Maak in Notion die databasis as ’n volle bladsy oop, kies ••• en Export, kies Markdown & CSV en kies die afgelaaide .zip-lêer, of een databasis-CSV daaruit, of plak daardie CSV. ’n Kolom genaamd Status word die lyste (as daar nie een is nie, word die eerste kolom wat soos ’n keuseveld lyk gebruik, en die invoerverslag sê watter een); rye word kaarte met hul titel, etikette, mense as lede, datums en die bladsyteks as die beskrywing; ander kolomme word pasgemaakte velde. Verwantskappe, beelde en aanhegsels word nie ingevoer nie.",
"import-board-instruction-plane": "Maak in Plane Workspace Settings oop, kies Exports, voer die projekte as JSON, CSV of Excel uit en laai die .zip-lêer af; kies dan daardie lêer, of een lêer daaruit, of plak die JSON of CSV. Toestande word lyste, projekte word swembane en werkitems word kaarte met hul identifiseerder, oueritem, toegewysde persone, etikette, datums, skakels en opmerkings; prioriteit, raming, siklus en module word pasgemaakte velde. Plane se uitvoer bevat geen beskrywings of aanhegsels nie, dus word hulle nie ingevoer nie.",
"import-board-instruction-fizzy": "Voer in Fizzy die rekening uit in \"Account settings\", of jou eie kaarte met \"Download my data\", en kies die .zip-lêer wat Fizzy vir jou stuur, of een kaart se .json-lêer. Borde word swembane en kolomme word lyste, met \"Maybe?\", \"Not now\" en \"Done\" soos in Fizzy; kaarte behou hul beskrywing, etikette, gevolmagtigdes, stappe as 'n kontrolelys, kommentaar en lêers.",
"import-board-instruction-mail": "Kies 'n .mbox-lêer, soos Thunderbird, Apple Mail, mutt of Gmail dit deur Google Takeout stoor, of 'n enkele .eml-boodskap, of plak die teks daarvan. Elke gesprek word een kaart in die Inbox-lys, met sy sender, ontvangers en onderwerp, sodat dit in die Email-aansig wys; die antwoorde word sy kommentaar. Gmail-etikette word etikette. Aanhegsels word nie ingevoer nie.",
"import-board-instruction-ical": "Kies 'n .ics-kalenderlêer, soos Google Calendar, Apple Calendar of Reminders, Thunderbird, Nextcloud of Outlook dit uitvoer, of plak die teks daarvan. Take gaan na To Do, In Progress, Done of Cancelled volgens hul status, en gebeurtenisse na Events, met hul begin- en sperdatums, sodat hulle in die Calendar- en Gantt-aansigte wys. Kategorieë en prioriteit word etikette. Herhalende items word een keer ingevoer.",
"import-board-instruction-googletakeout": "Kies by takeout.google.com Tasks, Keep, Mail, Calendar en Google Chat, skep die uitvoer en laai die .zip-lêer af, en kies dit dan hier. Elke produk word 'n swembaan: pos vir die Email-aansig, taaklyste en notas met hul kontrolelyste, kalendergebeurtenisse en take met datums, en kletsruimtes waarvan die boodskappe kommentaar is vir die Chat-aansig. Ander produkte en aanhegsels word nie ingevoer nie.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Maak in Telegram Desktop Settings, Advanced, Export Telegram data oop, kies die JSON-formaat en voer uit, kies dan die result.json-lêer, of plak die teks daarvan. Elke klets word 'n kaart in Direct messages, Groups of Channels, en sy boodskappe word die kaart se kommentaar, sodat die Chat-aansig die klets wys. Foto's en lêers word nie ingevoer nie.",
"import-board-instruction-whatsapp": "Maak in WhatsApp die klets oop, kies Export chat sonder media, en kies die .txt-lêer hier, of plak die teks daarvan. Die klets word 'n kaart waarvan die boodskappe sy kommentaar is, volgens hul sender en tyd, sodat die Chat-aansig dit wys. Media en stelselboodskappe word nie ingevoer nie.",
"import-board-instruction-discord": "Voer 'n Discord-kanaal uit met DiscordChatExporter in die JSON-formaat en kies die .json-lêer, of plak die teks daarvan. Die kanaal word 'n kaart in sy kategorie, en sy boodskappe word die kaart se kommentaar, sodat die Chat-aansig die kanaal wys. Die bediener word die swembaan. Aanhegsels word nie ingevoer nie.",
"import-board-instruction-rocketchat": "Voer in Rocket.Chat jou data as JSON uit in \"My Data\" en kies die .zip-lêer wat dit vir jou stuur, of een kamer se uitgevoerde .json-lêer. Elke kamer word 'n kaart en sy boodskappe word die kaart se kommentaar, sodat die Chat-aansig die kamer wys. Die .zip wat WeKan vir Rocket.Chat se CSV-invoerder uitvoer, word ook gelees.",
"import-board-instruction-evernote": "Voer in Evernote die notas of 'n notaboek uit as 'n .enex-lêer en kies dit hier, of plak die teks daarvan. Elke nota word 'n kaart met sy teks, sy taak-merkblokkies as 'n kontrolelys, sy merkers as etikette en sy herinnering as die sperdatum; notas waarvan die herinnering klaar is, gaan na Done. Prente en aangehegte lêers word nie ingevoer nie.",
"tool-group-kanban": "Kanban- en projekgereedskap",
"tool-group-issues": "Probleemvolgers en weergawebeheer",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Maak in Redmine die projek se Issues oop, kies Also available in: CSV onderaan die lys, kies die kolomme (All columns, met Description) en voer uit; plak dan die CSV. Redmine benoem die kolomme in jou taal, dus stel jou taal voor uitvoer op Engels in My account. Elke toestand word 'n lys en kwessies word kaarte met die tracker as 'n etiket, gevolmagtigde, outeur, datums, ouertaak en verwante kwessies; prioriteit, kategorie, teikenweergawe, beraamde tyd, % Done en pasgemaakte velde word pasgemaakte velde.",
"import-board-instruction-notion": "Maak in Notion die databasis as 'n volle bladsy oop, kies ••• en Export, kies Markdown & CSV en kies die .zip-lêer wat afgelaai word, of een databasis-CSV daaruit, of plak daardie CSV. 'n Kolom met die naam Status word die lyste (sonder een word die eerste kolom wat soos 'n keuseveld lyk, gebruik, en die invoerverslag sê watter een); rye word kaarte met hul titel, etikette, mense as lede, datums en die bladsyteks as beskrywing; ander kolomme word pasgemaakte velde. Verhoudings, prente en aanhegsels word nie ingevoer nie.",
"import-board-instruction-plane": "Maak in Plane Workspace Settings oop, kies Exports, voer die projekte as JSON, CSV of Excel uit en laai die .zip-lêer af; kies dan daardie lêer, of een lêer daarin, of plak die JSON of CSV. Toestande word lyste, projekte word swembane en kwessies word kaarte met hul identifiseerder, ouer, gevolmagtigdes, etikette, datums, skakels en opmerkings; prioriteit, skatting, siklus en module word pasgemaakte velde. Plane se uitvoer bevat geen beskrywings of aanhegsels nie, dus word hulle nie ingevoer nie.",
"import-board-instruction-fizzy": "Voer in Fizzy die rekening uit in \"Account settings\", of jou eie kaarte met \"Download my data\", en kies die .zip-lêer wat Fizzy vir jou stuur, of een kaart se .json-lêer. Borde word swembane en kolomme word lyste, met \"Maybe?\", \"Not now\" en \"Done\" soos in Fizzy; kaarte behou hul beskrywing, etikette, gevolmagtigdes, stappe as 'n kontrolelys, kommentaar en lêers.",
"import-board-instruction-mail": "Kies 'n .mbox-lêer, soos Thunderbird, Apple Mail, mutt of Gmail dit deur Google Takeout stoor, of 'n enkele .eml-boodskap, of plak die teks daarvan. Elke gesprek word een kaart in die Inbox-lys, met sy sender, ontvangers en onderwerp, sodat dit in die Email-aansig wys; die antwoorde word sy kommentaar. Gmail-etikette word etikette. Aanhegsels word nie ingevoer nie.",
"import-board-instruction-ical": "Kies 'n .ics-kalenderlêer, soos Google Calendar, Apple Calendar of Reminders, Thunderbird, Nextcloud of Outlook dit uitvoer, of plak die teks daarvan. Take gaan na To Do, In Progress, Done of Cancelled volgens hul status, en gebeurtenisse na Events, met hul begin- en sperdatums, sodat hulle in die Calendar- en Gantt-aansigte wys. Kategorieë en prioriteit word etikette. Herhalende items word een keer ingevoer.",
"import-board-instruction-googletakeout": "Kies by takeout.google.com Tasks, Keep, Mail, Calendar en Google Chat, skep die uitvoer en laai die .zip-lêer af, en kies dit dan hier. Elke produk word 'n swembaan: pos vir die Email-aansig, taaklyste en notas met hul kontrolelyste, kalendergebeurtenisse en take met datums, en kletsruimtes waarvan die boodskappe kommentaar is vir die Chat-aansig. Ander produkte en aanhegsels word nie ingevoer nie.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Maak in Telegram Desktop Settings, Advanced, Export Telegram data oop, kies die JSON-formaat en voer uit, kies dan die result.json-lêer, of plak die teks daarvan. Elke klets word 'n kaart in Direct messages, Groups of Channels, en sy boodskappe word die kaart se kommentaar, sodat die Chat-aansig die klets wys. Foto's en lêers word nie ingevoer nie.",
"import-board-instruction-whatsapp": "Maak in WhatsApp die klets oop, kies Export chat sonder media, en kies die .txt-lêer hier, of plak die teks daarvan. Die klets word 'n kaart waarvan die boodskappe sy kommentaar is, volgens hul sender en tyd, sodat die Chat-aansig dit wys. Media en stelselboodskappe word nie ingevoer nie.",
"import-board-instruction-discord": "Voer 'n Discord-kanaal uit met DiscordChatExporter in die JSON-formaat en kies die .json-lêer, of plak die teks daarvan. Die kanaal word 'n kaart in sy kategorie, en sy boodskappe word die kaart se kommentaar, sodat die Chat-aansig die kanaal wys. Die bediener word die swembaan. Aanhegsels word nie ingevoer nie.",
"import-board-instruction-rocketchat": "Voer in Rocket.Chat jou data as JSON uit in \"My Data\" en kies die .zip-lêer wat dit vir jou stuur, of een kamer se uitgevoerde .json-lêer. Elke kamer word 'n kaart en sy boodskappe word die kaart se kommentaar, sodat die Chat-aansig die kamer wys. Die .zip wat WeKan vir Rocket.Chat se CSV-invoerder uitvoer, word ook gelees.",
"import-board-instruction-evernote": "Voer in Evernote die notas of 'n notaboek uit as 'n .enex-lêer en kies dit hier, of plak die teks daarvan. Elke nota word 'n kaart met sy teks, sy taak-merkblokkies as 'n kontrolelys, sy merkers as etikette en sy herinnering as die sperdatum; notas waarvan die herinnering klaar is, gaan na Done. Prente en aangehegte lêers word nie ingevoer nie.",
"tool-group-kanban": "Kanban- en projekgereedskap",
"tool-group-issues": "Probleemvolgers en weergawebeheer",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Wɔ Redmine mu, bue prɔgyɛkt no Issues, paw Also available in: CSV wɔ nhwɛso no ase, paw kɔlɔm no (All columns, a Description ka ho) na yi adi, afei fa CSV no hyɛ mu. Redmine de wo kasa to kɔlɔm no din, enti sesa wo kasa kɔ Borɔfo wɔ My account mu ansa na woayi adi. Tebea biara bɛyɛ nhwɛso na nsɛm bɛyɛ kaad, a tracker no sɛ nsɛnkyerɛnne, nea wɔde adwuma ama no, ɔkyerɛwfoɔ, nna, adwuma a ɛyɛ agya ne nsɛm a ɛfa ho ka ho; nea ɛdi kan, nkyekyɛmu, ɔsɛsoɔ a wɔrebɔ ho mmɔden, berɛ a wɔasusu, % Done ne wo ankasa mmeae bɛyɛ wo ankasa mmeae.",
"import-board-instruction-notion": "Wɔ Notion mu, bue database no sɛ krataafa a ɛyɛ ma, paw ••• ne Export, paw Markdown & CSV, na paw .zip fael a ɛtwe no, anaa database CSV baako a ɛwɔ mu, anaa fa saa CSV no hyɛ mu. Kɔlɔm a ne din de Status bɛyɛ nhwɛso no (sɛ ɛnni hɔ a, kɔlɔm a ɛdi kan a ɛte sɛ apaweɛ na ɛbɛyɛ, na nsɛm a ɛfa fa ba mu ho no bɛka deɛ ɛyɛ); nsensanee bɛyɛ kaad a wɔn din, nsɛnkyerɛnne, nnipa sɛ amanfoɔ, nna, ne krataafa no nkyerɛwee sɛ nkyerɛkyerɛmu ka ho; kɔlɔm foforɔ bɛyɛ wo ankasa mmeae. Wɔmfa abusuabɔ, mfonini ne nneɛma a wɔde aka ho mma mu.",
"import-board-instruction-plane": "Wɔ Plane mu, bue Workspace Settings, paw Exports, yi prɔgyɛkt no adi sɛ JSON, CSV anaa Excel na twe .zip fael no, afei paw saa fael no, anaa fael baako a ɛwɔ mu, anaa fa JSON anaa CSV no hyɛ mu. Tebea ahodoɔ bɛyɛ nhwɛso, prɔgyɛkt bɛyɛ akwan, na nsɛm bɛyɛ kaad a wɔn nsɛnkyerɛnne nɔma, agya, wɔn a wɔde adwuma ama wɔn, nsɛnkyerɛnne, nna, linki ne nsusuiɛ ka ho; nea ɛdi kan, nsusuiɛ, kyinhyia ne module bɛyɛ wo ankasa mmeae. Plane deɛ a wɔyi adi nni nkyerɛkyerɛmu anaa nneɛma a wɔde aka ho, enti wɔmfa mma mu.",
"import-board-instruction-fizzy": "Wɔ Fizzy mu, yi akawnt no fi wɔ \"Account settings\" mu, anaa wo ankasa wo kaad ahodoɔ fa \"Download my data\" so, na paw .zip fael a Fizzy de bɛmena wo no, anaa kaad baako .json fael. Bɔɔd ahodoɔ bɛyɛ akwan na nkyerɛwee bɛyɛ nhwɛso ahodoɔ, a \"Maybe?\", \"Not now\" ne \"Done\" te sɛ wɔ Fizzy mu; kaad ahodoɔ kura wɔn nkyerɛkyerɛmu, nsɛnkyerɛnne, nnipa a wɔde adwuma ama wɔn, anammɔn sɛ nhwehwɛmu nhwɛso, nsusuiɛ ne fael.",
"import-board-instruction-mail": "Paw .mbox fael, sɛnea Thunderbird, Apple Mail, mutt anaa Gmail fa Google Takeout so kora no, anaa .eml nkra baako, anaa fa ne nsɛm no hyɛ mu. Nkɔmmɔbɔ biara bɛyɛ kaad baako wɔ Inbox nhwɛso no mu, ne nea ɔde mane, nea wɔde kɔma ne asɛmti, sɛnea ɛbɛda adi wɔ Email nhwɛe no mu; mmuae no bɛyɛ ne nsusuiɛ. Gmail nsɛnkyerɛnne bɛyɛ nsɛnkyerɛnne. Wɔmfa nneɛma a wɔde aka ho mmra mu.",
"import-board-instruction-ical": "Paw .ics kalenda fael, sɛnea Google Calendar, Apple Calendar anaa Reminders, Thunderbird, Nextcloud anaa Outlook yi no fi, anaa fa ne nsɛm no hyɛ mu. Nnwuma kɔ To Do, In Progress, Done anaa Cancelled sɛnea wɔn tebea te, na dwumadi kɔ Events, ne wɔn mfiase ne bere a ɛsɛ sɛ wowie, sɛnea ɛbɛda adi wɔ Calendar ne Gantt nhwɛe no mu. Nkyekyɛmu ne nea edi kan bɛyɛ nsɛnkyerɛnne. Nneɛma a ɛsan ba no, wɔde ba mu prɛko pɛ.",
"import-board-instruction-googletakeout": "Wɔ takeout.google.com, paw Tasks, Keep, Mail, Calendar ne Google Chat, yɛ export no na twe .zip fael no, afei paw wɔ ha. Adwuma biara bɛyɛ ɔkwan: krataa ma Email nhwɛe no, nnwuma nhwɛso ne nsɛm a wɔakyerɛw ne wɔn nhwehwɛmu nhwɛso, kalenda dwumadi ne nnwuma a ɛwɔ da, ne nkɔmmɔbɔ beae a wɔn nkra yɛ nsusuiɛ ma Chat nhwɛe no. Wɔmfa nneɛma afoforo ne nneɛma a wɔde aka ho mmra mu.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Wɔ Telegram Desktop mu, bue Settings, Advanced, Export Telegram data, paw JSON ɔkwan na yi fi, afei paw result.json fael no, anaa fa ne nsɛm no hyɛ mu. Nkɔmmɔbɔ biara bɛyɛ kaad wɔ Direct messages, Groups anaa Channels mu, na ne nkra bɛyɛ kaad no nsusuiɛ, sɛnea Chat nhwɛe no bɛkyerɛ nkɔmmɔbɔ no. Wɔmfa mfonini ne fael mmra mu.",
"import-board-instruction-whatsapp": "Wɔ WhatsApp mu, bue nkɔmmɔbɔ no, paw Export chat a media nni mu, na paw .txt fael no wɔ ha, anaa fa ne nsɛm no hyɛ mu. Nkɔmmɔbɔ no bɛyɛ kaad a ne nkra yɛ ne nsusuiɛ, sɛnea nea ɔde mane ne bere no te, sɛnea Chat nhwɛe no bɛkyerɛ. Wɔmfa media ne sistem nkra mmra mu.",
"import-board-instruction-discord": "Fa DiscordChatExporter yi Discord channel fi wɔ JSON ɔkwan so na paw .json fael no, anaa fa ne nsɛm no hyɛ mu. Channel no bɛyɛ kaad wɔ ne nkyekyɛmu mu, na ne nkra bɛyɛ kaad no nsusuiɛ, sɛnea Chat nhwɛe no bɛkyerɛ channel no. Server no bɛyɛ ɔkwan no. Wɔmfa nneɛma a wɔde aka ho mmra mu.",
"import-board-instruction-rocketchat": "Wɔ Rocket.Chat mu, yi wo data fi sɛ JSON wɔ \"My Data\" mu na paw .zip fael a ɛde bɛmena wo no, anaa dan baako .json fael a wɔayi afi. Dan biara bɛyɛ kaad na ne nkra bɛyɛ kaad no nsusuiɛ, sɛnea Chat nhwɛe no bɛkyerɛ dan no. Wɔkenkan .zip a WeKan yi ma Rocket.Chat CSV importer no nso.",
"import-board-instruction-evernote": "Wɔ Evernote mu, yi nsɛm a wɔakyerɛw anaa nhoma baako fi sɛ .enex fael na paw wɔ ha, anaa fa ne nsɛm no hyɛ mu. Nsɛm biara bɛyɛ kaad a ne nsɛm, ne to-do adaka sɛ nhwehwɛmu nhwɛso, ne tags sɛ nsɛnkyerɛnne ne ne nkaebɔ sɛ bere a ɛsɛ sɛ wowie; nsɛm a ne nkaebɔ awie no kɔ Done. Wɔmfa mfonini ne fael a wɔde aka ho mmra mu.",
"tool-group-kanban": "Kanban ne adwuma nnwinnade",
"tool-group-issues": "Ɔhaw akyidifoɔ ne nsakrae so hwɛ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "በRedmine ውስጥ የፕሮጀክቱን Issues ይክፈቱ፣ በዝርዝሩ ግርጌ Also available in: CSV ን ይምረጡ፣ አምዶቹን ይምረጡ (All columns፣ ከDescription ጋር) እና ይላኩ፣ ከዚያም CSV ን ይለጥፉ። Redmine አምዶቹን በእርስዎ ቋንቋ ይሰይማል፣ ስለዚህ ከመላክዎ በፊት በMy account ውስጥ ቋንቋዎን ወደ እንግሊዝኛ ያድርጉ። እያንዳንዱ ሁኔታ ዝርዝር ይሆናል፣ ጉዳዮችም ከትራከሩ እንደ መለያ፣ ኃላፊ፣ ደራሲ፣ ቀኖች፣ የወላጅ ተግባር እና ተዛማጅ ጉዳዮች ጋር ካርዶች ይሆናሉ፤ ቅድሚያ፣ ምድብ፣ የታለመ ስሪት፣ የተገመተ ጊዜ፣ % Done እና ብጁ መስኮች ብጁ መስኮች ይሆናሉ።",
"import-board-instruction-notion": "በNotion ውስጥ የውሂብ ጎታውን እንደ ሙሉ ገጽ ይክፈቱ፣ ••• እና Export ን ይምረጡ፣ Markdown & CSV ን ይምረጡ፣ እና የሚያወርደውን .zip ፋይል፣ ወይም ከውስጡ አንድ የውሂብ ጎታ CSV ይምረጡ፣ ወይም ያንን CSV ይለጥፉ። Status የሚባል አምድ ዝርዝሮች ይሆናል (ከሌለ፣ እንደ ምርጫ የሚመስለው የመጀመሪያው አምድ ይሆናል፣ የማስመጣት ሪፖርቱም የትኛው እንደሆነ ይናገራል)፤ ረድፎች ከርዕሳቸው፣ መለያዎች እንደ መለያዎች፣ ሰዎች እንደ አባላት፣ ቀኖች እና የገጹ ጽሑፍ እንደ መግለጫ ጋር ካርዶች ይሆናሉ፤ ሌሎች አምዶች ብጁ መስኮች ይሆናሉ። ግንኙነቶች፣ ምስሎች እና አባሪዎች አይገቡም።",
"import-board-instruction-plane": "በPlane ውስጥ Workspace Settings ን ይክፈቱ፣ Exports ን ይምረጡ፣ ፕሮጀክቶቹን እንደ JSON፣ CSV ወይም Excel ይላኩ እና የ.zip ፋይሉን ያውርዱ፣ ከዚያም ያንን ፋይል፣ ወይም ከውስጡ አንድ ፋይል ይምረጡ፣ ወይም JSON ወይም CSV ን ይለጥፉ። ሁኔታዎች ዝርዝሮች ይሆናሉ፣ ፕሮጀክቶች መስመሮች ይሆናሉ፣ ጉዳዮችም ከመለያ ቁጥራቸው፣ ወላጃቸው፣ ኃላፊዎቻቸው፣ መለያዎቻቸው፣ ቀኖቻቸው፣ አገናኞቻቸው እና አስተያየቶቻቸው ጋር ካርዶች ይሆናሉ፤ ቅድሚያ፣ ግምት፣ ዑደት እና ሞጁል ብጁ መስኮች ይሆናሉ። የPlane መላኪያ መግለጫዎች ወይም አባሪዎች የሉትም፣ ስለዚህ አይገቡም።",
"import-board-instruction-fizzy": "በFizzy ውስጥ፣ አካውንቱን በ\"Account settings\" ወደ ውጭ ይላኩ፣ ወይም የራስዎን ካርዶች በ\"Download my data\"፣ እና Fizzy የሚልክልዎትን የ.zip ፋይል ወይም የአንድ ካርድ .json ፋይል ይምረጡ። ሰሌዳዎች መስመሮች ይሆናሉ፣ አምዶችም ዝርዝሮች ይሆናሉ፣ \"Maybe?\"፣ \"Not now\" እና \"Done\" እንደ Fizzy ሆነው፤ ካርዶች መግለጫቸውን፣ መለያዎቻቸውን፣ ኃላፊዎቻቸውን፣ ደረጃዎችን እንደ የማረጋገጫ ዝርዝር፣ አስተያየቶችን እና ፋይሎችን ይይዛሉ።",
"import-board-instruction-mail": "Thunderbird፣ Apple Mail፣ mutt ወይም Gmail በGoogle Takeout በኩል እንደሚያስቀምጡት ያለ .mbox ፋይል፣ ወይም አንድ .eml መልእክት ይምረጡ፣ ወይም ጽሑፉን ይለጥፉ። እያንዳንዱ ውይይት ከላኪው፣ ከተቀባዮቹ እና ከርዕሱ ጋር በInbox ዝርዝር ውስጥ አንድ ካርድ ይሆናል፣ ስለዚህ በEmail እይታ ውስጥ ይታያል፤ ምላሾቹ አስተያየቶቹ ይሆናሉ። የGmail መለያዎች መለያዎች ይሆናሉ። አባሪዎች አይመጡም።",
"import-board-instruction-ical": "Google Calendar፣ Apple Calendar ወይም Reminders፣ Thunderbird፣ Nextcloud ወይም Outlook እንደሚያወጡት ያለ .ics የቀን መቁጠሪያ ፋይል ይምረጡ፣ ወይም ጽሑፉን ይለጥፉ። ተግባራት በሁኔታቸው መሠረት ወደ To Do፣ In Progress፣ Done ወይም Cancelled፣ ክስተቶች ደግሞ ወደ Events ይሄዳሉ፣ ከመጀመሪያ እና የማብቂያ ቀኖቻቸው ጋር፣ ስለዚህ በCalendar እና Gantt እይታዎች ውስጥ ይታያሉ። ምድቦች እና ቅድሚያ መለያዎች ይሆናሉ። የሚደጋገሙ ንጥሎች አንድ ጊዜ ብቻ ይመጣሉ።",
"import-board-instruction-googletakeout": "በtakeout.google.com ላይ Tasks፣ Keep፣ Mail፣ Calendar እና Google Chatን ይምረጡ፣ ወደ ውጭ መላኩን ይፍጠሩ እና የ.zip ፋይሉን ያውርዱ፣ ከዚያ እዚህ ይምረጡት። እያንዳንዱ ምርት መስመር ይሆናል፦ ደብዳቤ ለEmail እይታ፣ የተግባር ዝርዝሮች እና ማስታወሻዎች ከማረጋገጫ ዝርዝሮቻቸው ጋር፣ የቀን መቁጠሪያ ክስተቶች እና ተግባራት ከቀኖች ጋር፣ እና መልእክቶቻቸው ለChat እይታ አስተያየቶች የሆኑ የውይይት ቦታዎች። ሌሎች ምርቶች እና አባሪዎች አይመጡም።",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "በTelegram Desktop ውስጥ Settings፣ Advanced፣ Export Telegram data ይክፈቱ፣ የJSON ቅርጸትን ይምረጡ እና ወደ ውጭ ይላኩ፣ ከዚያ result.json ፋይሉን ይምረጡ፣ ወይም ጽሑፉን ይለጥፉ። እያንዳንዱ ውይይት በDirect messages፣ Groups ወይም Channels ውስጥ ካርድ ይሆናል፣ መልእክቶቹም የካርዱ አስተያየቶች ይሆናሉ፣ ስለዚህ የChat እይታ ውይይቱን ያሳያል። ፎቶዎች እና ፋይሎች አይመጡም።",
"import-board-instruction-whatsapp": "በWhatsApp ውስጥ ውይይቱን ይክፈቱ፣ ያለ ሚዲያ Export chat ይምረጡ፣ እና የ.txt ፋይሉን እዚህ ይምረጡ፣ ወይም ጽሑፉን ይለጥፉ። ውይይቱ መልእክቶቹ በላኪያቸው እና በጊዜያቸው አስተያየቶቹ የሆኑ ካርድ ይሆናል፣ ስለዚህ የChat እይታ ያሳየዋል። ሚዲያ እና የስርዓት መልእክቶች አይመጡም።",
"import-board-instruction-discord": "የDiscord ቻናልን በDiscordChatExporter በJSON ቅርጸት ወደ ውጭ ይላኩ እና የ.json ፋይሉን ይምረጡ፣ ወይም ጽሑፉን ይለጥፉ። ቻናሉ በምድቡ ውስጥ ካርድ ይሆናል፣ መልእክቶቹም የካርዱ አስተያየቶች ይሆናሉ፣ ስለዚህ የChat እይታ ቻናሉን ያሳያል። አገልጋዩ መስመሩ ይሆናል። አባሪዎች አይመጡም።",
"import-board-instruction-rocketchat": "በRocket.Chat ውስጥ፣ ውሂብዎን በ\"My Data\" ውስጥ እንደ JSON ወደ ውጭ ይላኩ እና የሚልክልዎትን የ.zip ፋይል ወይም የአንድ ክፍል ወደ ውጭ የተላከ .json ፋይል ይምረጡ። እያንዳንዱ ክፍል ካርድ ይሆናል፣ መልእክቶቹም የካርዱ አስተያየቶች ይሆናሉ፣ ስለዚህ የChat እይታ ክፍሉን ያሳያል። WeKan ለRocket.Chat CSV አስመጪ ወደ ውጭ የሚልከው .zip እንዲሁ ይነበባል።",
"import-board-instruction-evernote": "በEvernote ውስጥ ማስታወሻዎቹን ወይም ማስታወሻ ደብተርን እንደ .enex ፋይል ወደ ውጭ ይላኩ እና እዚህ ይምረጡት፣ ወይም ጽሑፉን ይለጥፉ። እያንዳንዱ ማስታወሻ ከጽሑፉ፣ ከማረጋገጫ ሳጥኖቹ እንደ የማረጋገጫ ዝርዝር፣ ከታጎቹ እንደ መለያዎች እና ከአስታዋሹ እንደ የማብቂያ ጊዜ ጋር ካርድ ይሆናል፤ አስታዋሻቸው የተጠናቀቀ ማስታወሻዎች ወደ Done ይሄዳሉ። ምስሎች እና የተያያዙ ፋይሎች አይመጡም።",
"tool-group-kanban": "የKanban እና የፕሮጀክት መሣሪያዎች",
"tool-group-issues": "የችግር መከታተያዎች እና የስሪት ቁጥጥር",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "En Redmine, ubre as Issues d'o prochecto, tría Also available in: CSV en o baixo d'a lista, eslei as columnas (All columns, con Description) y exporta, dimpués apega o CSV. Redmine nombra as columnas en a tuya luenga, asinas que meteba a tuya luenga en anglés en My account antes d'exportar. Cada estau se torna una lista y as incidencias se tornan tarchetas, con o tracker como etiqueta, asignau, autor, calendatas, tarea pai y incidencias relacionadas; prioridat, categoría, versión obchectivo, tiempo estimau, % Done y campos personalizaus se tornan campos personalizaus.",
"import-board-instruction-notion": "En Notion, ubre a base de datos como pachina completa, tría ••• y Export, eslei Markdown & CSV, y tría o fichero .zip que se descarga, u un CSV de base de datos d'adintro, u apega ixe CSV. Una columna clamada Status se torna as listas (si no i ye, la fa a primer columna que pareixe una selección, y o informe d'importación diz quala); as filas se tornan tarchetas con o suyo titol, etiquetas como etiquetas, personas como miembros, calendatas, y o texto d'a pachina como descripción; as atras columnas se tornan campos personalizaus. As relacions, imachens y adchuntos no s'importan.",
"import-board-instruction-plane": "En Plane, ubre Workspace Settings, tría Exports, exporta os prochectos como JSON, CSV u Excel y descarga o fichero .zip, dimpués tría ixe fichero, u un fichero d'adintro, u apega o JSON u o CSV. Os estaus se tornan listas, os prochectos se tornan carrils, y as incidencias se tornan tarchetas con o suyo identificador, pai, asignaus, etiquetas, calendatas, vinclos y comentarios; prioridat, estimación, cicle y modulo se tornan campos personalizaus. A exportación de Plane no tiene descripcions ni adchuntos, asinas que no s'importan.",
"import-board-instruction-fizzy": "En Fizzy, exporta a cuenta en «Account settings», u as tuyas tarchetas con «Download my data», y tría o fichero .zip que te ninvia Fizzy, u o fichero .json d'una tarcheta. Os tableros se tornan carrils y as columnas se tornan listas, con «Maybe?», «Not now» y «Done» como en Fizzy; as tarchetas mantienen a suya descripción, etiquetas, asignaus, pasos como lista de comprebación, comentarios y fichers.",
"import-board-instruction-mail": "Tría un fichero .mbox, como lo alzan Thunderbird, Apple Mail, mutt u Gmail a traviés de Google Takeout, u un solo mensache .eml, u apega o suyo texto. Cada conversación se torna una tarcheta en a lista Inbox, con o suyo remitent, destinatarios y asunto, ta que se veiga en a vista Email; as respuestas se tornan os suyos comentarios. As etiquetas de Gmail se tornan etiquetas. Os adchuntos no s'importan.",
"import-board-instruction-ical": "Tría un fichero de calendario .ics, como lo exportan Google Calendar, Apple Calendar u Reminders, Thunderbird, Nextcloud u Outlook, u apega o suyo texto. As tascas van ta To Do, In Progress, Done u Cancelled seguntes o suyo estau, y os eventos ta Events, con as suyas calendatas de inicio y de vencimiento, ta que se veigan en as vistas Calendar y Gantt. As categorías y a prioridat se tornan etiquetas. Os elementos que se repiten s'importan una vegada.",
"import-board-instruction-googletakeout": "En takeout.google.com, tría Tasks, Keep, Mail, Calendar y Google Chat, crea a exportación y descarga o fichero .zip, dimpués tría-lo aquí. Cada producto se torna un carril: o correu ta la vista Email, as listas de tascas y as notas con as suyas listas de comprebación, os eventos de calendario y as tascas con calendatas, y os espacios de chat que os suyos mensaches son comentarios ta la vista Chat. Atros productos y os adchuntos no s'importan.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "En Telegram Desktop, ubre Settings, Advanced, Export Telegram data, tría o formato JSON y exporta, dimpués tría o fichero result.json, u apega o suyo texto. Cada chat se torna una tarcheta en Direct messages, Groups u Channels, y os suyos mensaches se tornan os comentarios d'a tarcheta, ta que a vista Chat amuestre o chat. As fotos y os fichers no s'importan.",
"import-board-instruction-whatsapp": "En WhatsApp, ubre o chat, tría Export chat sin multimedia, y tría aquí o fichero .txt, u apega o suyo texto. O chat se torna una tarcheta que os suyos mensaches son os suyos comentarios, por o suyo remitent y hora, ta que a vista Chat lo amuestre. Os multimedia y os mensaches d'o sistema no s'importan.",
"import-board-instruction-discord": "Exporta un canal de Discord con DiscordChatExporter en o formato JSON y tría o fichero .json, u apega o suyo texto. O canal se torna una tarcheta en a suya categoría, y os suyos mensaches se tornan os comentarios d'a tarcheta, ta que a vista Chat amuestre o canal. O servidor se torna o carril. Os adchuntos no s'importan.",
"import-board-instruction-rocketchat": "En Rocket.Chat, exporta os tuyos datos como JSON en «My Data» y tría o fichero .zip que te ninvia, u o fichero .json exportau d'una sala. Cada sala se torna una tarcheta y os suyos mensaches se tornan os comentarios d'a tarcheta, ta que a vista Chat amuestre a sala. Tamién se leye o .zip que WeKan exporta ta l'importador CSV de Rocket.Chat.",
"import-board-instruction-evernote": "En Evernote, exporta as notas u un caderno como fichero .enex y tría-lo aquí, u apega o suyo texto. Cada nota se torna una tarcheta con o suyo texto, as suyas caixetas de tasca como lista de comprebación, as suyas etiquetas como etiquetas y o suyo recordatorio como calendata de vencimiento; as notas que o suyo recordatorio ye feito van ta Done. As imachens y os fichers adchuntos no s'importan.",
"tool-group-kanban": "Ferramientas Kanban y de prochectos",
"tool-group-issues": "Seguimiento d'incidencias y control de versions",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "في Redmine، افتح Issues الخاصة بالمشروع واختر Also available in: CSV أسفل القائمة، وحدد الأعمدة (All columns مع Description) وصدّرها، ثم الصق CSV. يسمّي Redmine الأعمدة بلغتك، لذا اضبط لغتك على الإنجليزية في My account قبل التصدير. تتحول كل حالة إلى قائمة والمسائل إلى بطاقات مع نوع التتبع كتسمية والمكلّف والمؤلف والتواريخ والمهمة الأصل والمسائل المرتبطة؛ وتتحول الأولوية والفئة والإصدار المستهدف والوقت المقدر و% Done والحقول المخصصة إلى حقول مخصصة.",
"import-board-instruction-notion": "في Notion، افتح قاعدة البيانات كصفحة كاملة واختر ••• ثم Export، واختر Markdown & CSV وحدد ملف .zip الذي يُنزّل، أو ملف CSV لقاعدة بيانات واحدة بداخله، أو الصق ذلك CSV. يتحول عمود اسمه Status إلى القوائم (وإن لم يوجد، يُستخدم أول عمود يبدو كحقل اختيار، ويبيّن تقرير الاستيراد أي عمود اختير)؛ وتتحول الصفوف إلى بطاقات مع عنوانها ووسومها كتسميات والأشخاص كأعضاء والتواريخ ونص الصفحة كوصف؛ وتتحول الأعمدة الأخرى إلى حقول مخصصة. لا تُستورد العلاقات أو الصور أو المرفقات.",
"import-board-instruction-plane": "في Plane، افتح Workspace Settings واختر Exports وصدّر المشاريع بصيغة JSON أو CSV أو Excel ونزّل ملف .zip، ثم اختر ذلك الملف أو أحد الملفات داخله، أو الصق JSON أو CSV. تتحول الحالات إلى قوائم والمشاريع إلى مسارات والمسائل إلى بطاقات مع المعرّف والأصل والمكلّفين والتسميات والتواريخ والروابط والتعليقات؛ وتتحول الأولوية والتقدير والدورة والوحدة إلى حقول مخصصة. لا يتضمن تصدير Plane أوصافًا أو مرفقات، ولذلك لا تُستورد.",
"import-board-instruction-fizzy": "في Fizzy، صدّر الحساب من «Account settings»، أو بطاقاتك الخاصة باستخدام «Download my data»، واختر ملف ‎.zip الذي يرسله لك Fizzy، أو ملف ‎.json لبطاقة واحدة. تصبح اللوحات خطوط سباحة وتصبح الأعمدة قائمات، مع «Maybe?» و«Not now» و«Done» كما في Fizzy؛ وتحتفظ البطاقات بوصفها وعلاماتها والمكلّفين بها والخطوات كقائمة تدقيق والتعليقات والملفات.",
"import-board-instruction-mail": "اختر ملف ‎.mbox كما يحفظه Thunderbird أو Apple Mail أو mutt أو Gmail عبر Google Takeout، أو رسالة ‎.eml واحدة، أو الصق نصه. تصبح كل محادثة بطاقة واحدة في قائمة Inbox، مع مرسلها ومستلميها وموضوعها، فتظهر في عرض Email؛ وتصبح الردود تعليقاتها. تصبح تسميات Gmail علامات. لا يتم استيراد المرفقات.",
"import-board-instruction-ical": "اختر ملف تقويم ‎.ics كما يصدّره Google Calendar أو Apple Calendar أو Reminders أو Thunderbird أو Nextcloud أو Outlook، أو الصق نصه. تذهب المهام إلى To Do أو In Progress أو Done أو Cancelled حسب حالتها، والأحداث إلى Events، مع تواريخ البدء والاستحقاق، فتظهر في عرضي Calendar وGantt. تصبح الفئات والأولوية علامات. تُستورد العناصر المتكررة مرة واحدة.",
"import-board-instruction-googletakeout": "في takeout.google.com اختر Tasks وKeep وMail وCalendar وGoogle Chat، وأنشئ التصدير ونزّل ملف ‎.zip، ثم اختره هنا. يصبح كل منتج خط سباحة: البريد لعرض Email، وقوائم المهام والملاحظات مع قوائم التدقيق الخاصة بها، وأحداث التقويم والمهام مع تواريخها، ومساحات الدردشة التي تكون رسائلها تعليقات لعرض Chat. لا يتم استيراد المنتجات الأخرى والمرفقات.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "في Telegram Desktop افتح Settings ثم Advanced ثم Export Telegram data، واختر تنسيق JSON وصدّر، ثم اختر ملف result.json، أو الصق نصه. تصبح كل دردشة بطاقة في Direct messages أو Groups أو Channels، وتصبح رسائلها تعليقات البطاقة، فيعرض Chat الدردشة. لا يتم استيراد الصور والملفات.",
"import-board-instruction-whatsapp": "في WhatsApp افتح الدردشة، واختر Export chat بدون وسائط، واختر ملف ‎.txt هنا، أو الصق نصه. تصبح الدردشة بطاقة تكون رسائلها تعليقاتها، باسم مرسلها ووقتها، فيعرضها Chat. لا يتم استيراد الوسائط ورسائل النظام.",
"import-board-instruction-discord": "صدّر قناة Discord باستخدام DiscordChatExporter بتنسيق JSON واختر ملف ‎.json، أو الصق نصه. تصبح القناة بطاقة في فئتها، وتصبح رسائلها تعليقات البطاقة، فيعرض Chat القناة. يصبح الخادم خط السباحة. لا يتم استيراد المرفقات.",
"import-board-instruction-rocketchat": "في Rocket.Chat، صدّر بياناتك بتنسيق JSON من «My Data» واختر ملف ‎.zip الذي يرسله لك، أو ملف ‎.json المصدَّر لغرفة واحدة. تصبح كل غرفة بطاقة وتصبح رسائلها تعليقات البطاقة، فيعرض Chat الغرفة. ويُقرأ أيضًا ملف ‎.zip الذي يصدّره WeKan لمستورد CSV في Rocket.Chat.",
"import-board-instruction-evernote": "في Evernote صدّر الملاحظات أو دفتر ملاحظات كملف ‎.enex واختره هنا، أو الصق نصه. تصبح كل ملاحظة بطاقة بنصها، ومربعات المهام فيها كقائمة تدقيق، ووسومها كعلامات، وتذكيرها كتاريخ استحقاق؛ والملاحظات التي اكتمل تذكيرها تذهب إلى Done. لا يتم استيراد الصور والملفات المرفقة.",
"tool-group-kanban": "أدوات كانبان وإدارة المشاريع",
"tool-group-issues": "متتبعات المشكلات والتحكم في الإصدارات",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "في Redmine، افتح Issues الخاصة بالمشروع واختر Also available in: CSV أسفل القائمة، وحدد الأعمدة (All columns مع Description) وصدّرها، ثم الصق CSV. يسمّي Redmine الأعمدة بلغتك، لذا اضبط لغتك على الإنجليزية في My account قبل التصدير. تتحول كل حالة إلى قائمة والمسائل إلى بطاقات مع نوع التتبع كتسمية والمكلّف والمؤلف والتواريخ والمهمة الأصل والمسائل المرتبطة؛ وتتحول الأولوية والفئة والإصدار المستهدف والوقت المقدر و% Done والحقول المخصصة إلى حقول مخصصة.",
"import-board-instruction-notion": "في Notion، افتح قاعدة البيانات كصفحة كاملة واختر ••• ثم Export، واختر Markdown & CSV وحدد ملف .zip الذي يُنزّل، أو ملف CSV لقاعدة بيانات واحدة بداخله، أو الصق ذلك CSV. يتحول عمود اسمه Status إلى القوائم (وإن لم يوجد، يُستخدم أول عمود يبدو كحقل اختيار، ويبيّن تقرير الاستيراد أي عمود اختير)؛ وتتحول الصفوف إلى بطاقات مع عنوانها ووسومها كتسميات والأشخاص كأعضاء والتواريخ ونص الصفحة كوصف؛ وتتحول الأعمدة الأخرى إلى حقول مخصصة. لا تُستورد العلاقات أو الصور أو المرفقات.",
"import-board-instruction-plane": "في Plane، افتح Workspace Settings واختر Exports وصدّر المشاريع بصيغة JSON أو CSV أو Excel ونزّل ملف .zip، ثم اختر ذلك الملف أو أحد الملفات داخله، أو الصق JSON أو CSV. تتحول الحالات إلى قوائم والمشاريع إلى مسارات والمسائل إلى بطاقات مع المعرّف والأصل والمكلّفين والتسميات والتواريخ والروابط والتعليقات؛ وتتحول الأولوية والتقدير والدورة والوحدة إلى حقول مخصصة. لا يتضمن تصدير Plane أوصافًا أو مرفقات، ولذلك لا تُستورد.",
"import-board-instruction-fizzy": "في Fizzy، صدّر الحساب من «Account settings»، أو بطاقاتك الخاصة باستخدام «Download my data»، واختر ملف ‎.zip الذي يرسله لك Fizzy، أو ملف ‎.json لبطاقة واحدة. تصبح اللوحات خطوط سباحة وتصبح الأعمدة قائمات، مع «Maybe?» و«Not now» و«Done» كما في Fizzy؛ وتحتفظ البطاقات بوصفها وعلاماتها والمكلّفين بها والخطوات كقائمة تدقيق والتعليقات والملفات.",
"import-board-instruction-mail": "اختر ملف ‎.mbox كما يحفظه Thunderbird أو Apple Mail أو mutt أو Gmail عبر Google Takeout، أو رسالة ‎.eml واحدة، أو الصق نصه. تصبح كل محادثة بطاقة واحدة في قائمة Inbox، مع مرسلها ومستلميها وموضوعها، فتظهر في عرض Email؛ وتصبح الردود تعليقاتها. تصبح تسميات Gmail علامات. لا يتم استيراد المرفقات.",
"import-board-instruction-ical": "اختر ملف تقويم ‎.ics كما يصدّره Google Calendar أو Apple Calendar أو Reminders أو Thunderbird أو Nextcloud أو Outlook، أو الصق نصه. تذهب المهام إلى To Do أو In Progress أو Done أو Cancelled حسب حالتها، والأحداث إلى Events، مع تواريخ البدء والاستحقاق، فتظهر في عرضي Calendar وGantt. تصبح الفئات والأولوية علامات. تُستورد العناصر المتكررة مرة واحدة.",
"import-board-instruction-googletakeout": "في takeout.google.com اختر Tasks وKeep وMail وCalendar وGoogle Chat، وأنشئ التصدير ونزّل ملف ‎.zip، ثم اختره هنا. يصبح كل منتج خط سباحة: البريد لعرض Email، وقوائم المهام والملاحظات مع قوائم التدقيق الخاصة بها، وأحداث التقويم والمهام مع تواريخها، ومساحات الدردشة التي تكون رسائلها تعليقات لعرض Chat. لا يتم استيراد المنتجات الأخرى والمرفقات.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "في Telegram Desktop افتح Settings ثم Advanced ثم Export Telegram data، واختر تنسيق JSON وصدّر، ثم اختر ملف result.json، أو الصق نصه. تصبح كل دردشة بطاقة في Direct messages أو Groups أو Channels، وتصبح رسائلها تعليقات البطاقة، فيعرض Chat الدردشة. لا يتم استيراد الصور والملفات.",
"import-board-instruction-whatsapp": "في WhatsApp افتح الدردشة، واختر Export chat بدون وسائط، واختر ملف ‎.txt هنا، أو الصق نصه. تصبح الدردشة بطاقة تكون رسائلها تعليقاتها، باسم مرسلها ووقتها، فيعرضها Chat. لا يتم استيراد الوسائط ورسائل النظام.",
"import-board-instruction-discord": "صدّر قناة Discord باستخدام DiscordChatExporter بتنسيق JSON واختر ملف ‎.json، أو الصق نصه. تصبح القناة بطاقة في فئتها، وتصبح رسائلها تعليقات البطاقة، فيعرض Chat القناة. يصبح الخادم خط السباحة. لا يتم استيراد المرفقات.",
"import-board-instruction-rocketchat": "في Rocket.Chat، صدّر بياناتك بتنسيق JSON من «My Data» واختر ملف ‎.zip الذي يرسله لك، أو ملف ‎.json المصدَّر لغرفة واحدة. تصبح كل غرفة بطاقة وتصبح رسائلها تعليقات البطاقة، فيعرض Chat الغرفة. ويُقرأ أيضًا ملف ‎.zip الذي يصدّره WeKan لمستورد CSV في Rocket.Chat.",
"import-board-instruction-evernote": "في Evernote صدّر الملاحظات أو دفتر ملاحظات كملف ‎.enex واختره هنا، أو الصق نصه. تصبح كل ملاحظة بطاقة بنصها، ومربعات المهام فيها كقائمة تدقيق، ووسومها كعلامات، وتذكيرها كتاريخ استحقاق؛ والملاحظات التي اكتمل تذكيرها تذهب إلى Done. لا يتم استيراد الصور والملفات المرفقة.",
"tool-group-kanban": "أدوات كانبان وإدارة المشاريع",
"tool-group-issues": "متتبعات المشكلات والتحكم في الإصدارات",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "في Redmine، افتح Issues الخاصة بالمشروع واختر Also available in: CSV أسفل القائمة، وحدد الأعمدة (All columns مع Description) وصدّرها، ثم الصق CSV. يسمّي Redmine الأعمدة بلغتك، لذا اضبط لغتك على الإنجليزية في My account قبل التصدير. تتحول كل حالة إلى قائمة والمسائل إلى بطاقات مع نوع التتبع كتسمية والمكلّف والمؤلف والتواريخ والمهمة الأصل والمسائل المرتبطة؛ وتتحول الأولوية والفئة والإصدار المستهدف والوقت المقدر و% Done والحقول المخصصة إلى حقول مخصصة.",
"import-board-instruction-notion": "في Notion، افتح قاعدة البيانات كصفحة كاملة واختر ••• ثم Export، واختر Markdown & CSV وحدد ملف .zip الذي يُنزّل، أو ملف CSV لقاعدة بيانات واحدة بداخله، أو الصق ذلك CSV. يتحول عمود اسمه Status إلى القوائم (وإن لم يوجد، يُستخدم أول عمود يبدو كحقل اختيار، ويبيّن تقرير الاستيراد أي عمود اختير)؛ وتتحول الصفوف إلى بطاقات مع عنوانها ووسومها كتسميات والأشخاص كأعضاء والتواريخ ونص الصفحة كوصف؛ وتتحول الأعمدة الأخرى إلى حقول مخصصة. لا تُستورد العلاقات أو الصور أو المرفقات.",
"import-board-instruction-plane": "في Plane، افتح Workspace Settings واختر Exports وصدّر المشاريع بصيغة JSON أو CSV أو Excel ونزّل ملف .zip، ثم اختر ذلك الملف أو أحد الملفات داخله، أو الصق JSON أو CSV. تتحول الحالات إلى قوائم والمشاريع إلى مسارات والمسائل إلى بطاقات مع المعرّف والأصل والمكلّفين والتسميات والتواريخ والروابط والتعليقات؛ وتتحول الأولوية والتقدير والدورة والوحدة إلى حقول مخصصة. لا يتضمن تصدير Plane أوصافًا أو مرفقات، ولذلك لا تُستورد.",
"import-board-instruction-fizzy": "في Fizzy، صدّر الحساب من «Account settings»، أو بطاقاتك الخاصة باستخدام «Download my data»، واختر ملف ‎.zip الذي يرسله لك Fizzy، أو ملف ‎.json لبطاقة واحدة. تصبح اللوحات خطوط سباحة وتصبح الأعمدة قائمات، مع «Maybe?» و«Not now» و«Done» كما في Fizzy؛ وتحتفظ البطاقات بوصفها وعلاماتها والمكلّفين بها والخطوات كقائمة تدقيق والتعليقات والملفات.",
"import-board-instruction-mail": "اختر ملف ‎.mbox كما يحفظه Thunderbird أو Apple Mail أو mutt أو Gmail عبر Google Takeout، أو رسالة ‎.eml واحدة، أو الصق نصه. تصبح كل محادثة بطاقة واحدة في قائمة Inbox، مع مرسلها ومستلميها وموضوعها، فتظهر في عرض Email؛ وتصبح الردود تعليقاتها. تصبح تسميات Gmail علامات. لا يتم استيراد المرفقات.",
"import-board-instruction-ical": "اختر ملف تقويم ‎.ics كما يصدّره Google Calendar أو Apple Calendar أو Reminders أو Thunderbird أو Nextcloud أو Outlook، أو الصق نصه. تذهب المهام إلى To Do أو In Progress أو Done أو Cancelled حسب حالتها، والأحداث إلى Events، مع تواريخ البدء والاستحقاق، فتظهر في عرضي Calendar وGantt. تصبح الفئات والأولوية علامات. تُستورد العناصر المتكررة مرة واحدة.",
"import-board-instruction-googletakeout": "في takeout.google.com اختر Tasks وKeep وMail وCalendar وGoogle Chat، وأنشئ التصدير ونزّل ملف ‎.zip، ثم اختره هنا. يصبح كل منتج خط سباحة: البريد لعرض Email، وقوائم المهام والملاحظات مع قوائم التدقيق الخاصة بها، وأحداث التقويم والمهام مع تواريخها، ومساحات الدردشة التي تكون رسائلها تعليقات لعرض Chat. لا يتم استيراد المنتجات الأخرى والمرفقات.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "في Telegram Desktop افتح Settings ثم Advanced ثم Export Telegram data، واختر تنسيق JSON وصدّر، ثم اختر ملف result.json، أو الصق نصه. تصبح كل دردشة بطاقة في Direct messages أو Groups أو Channels، وتصبح رسائلها تعليقات البطاقة، فيعرض Chat الدردشة. لا يتم استيراد الصور والملفات.",
"import-board-instruction-whatsapp": "في WhatsApp افتح الدردشة، واختر Export chat بدون وسائط، واختر ملف ‎.txt هنا، أو الصق نصه. تصبح الدردشة بطاقة تكون رسائلها تعليقاتها، باسم مرسلها ووقتها، فيعرضها Chat. لا يتم استيراد الوسائط ورسائل النظام.",
"import-board-instruction-discord": "صدّر قناة Discord باستخدام DiscordChatExporter بتنسيق JSON واختر ملف ‎.json، أو الصق نصه. تصبح القناة بطاقة في فئتها، وتصبح رسائلها تعليقات البطاقة، فيعرض Chat القناة. يصبح الخادم خط السباحة. لا يتم استيراد المرفقات.",
"import-board-instruction-rocketchat": "في Rocket.Chat، صدّر بياناتك بتنسيق JSON من «My Data» واختر ملف ‎.zip الذي يرسله لك، أو ملف ‎.json المصدَّر لغرفة واحدة. تصبح كل غرفة بطاقة وتصبح رسائلها تعليقات البطاقة، فيعرض Chat الغرفة. ويُقرأ أيضًا ملف ‎.zip الذي يصدّره WeKan لمستورد CSV في Rocket.Chat.",
"import-board-instruction-evernote": "في Evernote صدّر الملاحظات أو دفتر ملاحظات كملف ‎.enex واختره هنا، أو الصق نصه. تصبح كل ملاحظة بطاقة بنصها، ومربعات المهام فيها كقائمة تدقيق، ووسومها كعلامات، وتذكيرها كتاريخ استحقاق؛ والملاحظات التي اكتمل تذكيرها تذهب إلى Done. لا يتم استيراد الصور والملفات المرفقة.",
"tool-group-kanban": "أدوات كانبان وإدارة المشاريع",
"tool-group-issues": "متتبعات المشكلات والتحكم في الإصدارات",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "فRedmine، حل Issues ديال المشروع، ختار Also available in: CSV لتحت ديال القائمة، ختار الأعمدة (All columns، مع Description) وصدّر، ومن بعد لصق CSV. Redmine كيسمي الأعمدة باللغة ديالك، داكشي علاش بدّل اللغة ديالك للإنجليزية فMy account قبل التصدير. كل حالة كتولي قائمة والمشاكل كيوليو بطاقات، مع الـtracker بحال علامة، والمكلّف والكاتب والتواريخ والمهمة الأب والمشاكل المرتبطة؛ الأولوية والفئة والنسخة المستهدفة والوقت المقدّر و% Done والحقول المخصصة كيوليو حقول مخصصة.",
"import-board-instruction-notion": "فNotion، حل قاعدة البيانات بحال صفحة كاملة، ختار ••• وExport، ختار Markdown & CSV، وختار ملف .zip اللي كيتحمّل، ولا CSV ديال قاعدة بيانات وحدة منو، ولا لصق داك CSV. العمود اللي سميتو Status كيولي هو القوائم (إلا ما كانش، أول عمود كيشبه لاختيار هو اللي كيولي، وتقرير الاستيراد كيقول شكون)؛ السطور كيوليو بطاقات مع العنوان ديالهم، والوسوم بحال علامات، والناس بحال أعضاء، والتواريخ، والنص ديال الصفحة بحال وصف؛ الأعمدة الأخرى كيوليو حقول مخصصة. العلاقات والتصاور والمرفقات ما كتستوردش.",
"import-board-instruction-plane": "فPlane، حل Workspace Settings، ختار Exports، صدّر المشاريع بحال JSON ولا CSV ولا Excel وحمّل ملف .zip، ومن بعد ختار داك الملف، ولا ملف واحد من داخلو، ولا لصق JSON ولا CSV. الحالات كيوليو قوائم، المشاريع كيوليو مسارات، والمشاكل كيوليو بطاقات مع المعرّف والأب والمكلّفين والعلامات والتواريخ والروابط والتعليقات ديالهم؛ الأولوية والتقدير والدورة والوحدة كيوليو حقول مخصصة. التصدير ديال Plane ما فيهش الأوصاف ولا المرفقات، داكشي علاش ما كيتستوردوش.",
"import-board-instruction-fizzy": "ف Fizzy، صدر الحساب من «Account settings»، ولا البطاقات ديالك بـ «Download my data»، وختار الفيشي ‎.zip اللي كيصيفط ليك Fizzy، ولا الفيشي ‎.json ديال بطاقة وحدة. اللوحات كيوليو خطوط سباحة والأعمدة كيوليو قائمات، مع «Maybe?» و«Not now» و«Done» بحال ف Fizzy؛ والبطاقات كيحتافظو بالوصف ديالهم، العلامات، المكلفين، الخطوات بحال قائمة التدقيق، التعليقات والفيشيات.",
"import-board-instruction-mail": "ختار فيشي ‎.mbox كيف كيسجلوه Thunderbird ولا Apple Mail ولا mutt ولا Gmail عبر Google Takeout، ولا رسالة ‎.eml وحدة، ولا لصق النص ديالو. كل محادثة كتولي بطاقة وحدة فالليستة Inbox، مع اللي صيفطها واللي توصلو بيها والموضوع ديالها، باش تبان فالعرض Email؛ والجوابات كيوليو التعليقات ديالها. التسميات ديال Gmail كيوليو علامات. المرفقات ما كيتستوردوش.",
"import-board-instruction-ical": "ختار فيشي ديال التقويم ‎.ics كيف كيصدروه Google Calendar ولا Apple Calendar ولا Reminders ولا Thunderbird ولا Nextcloud ولا Outlook، ولا لصق النص ديالو. المهام كيمشيو لـ To Do ولا In Progress ولا Done ولا Cancelled على حساب الحالة ديالهم، والأحداث لـ Events، مع تاريخ البداية وتاريخ الاستحقاق، باش يبانو فالعروض Calendar و Gantt. الفئات والأولوية كيوليو علامات. الحوايج اللي كيتعاودو كيتستوردو مرة وحدة.",
"import-board-instruction-googletakeout": "فـ takeout.google.com، ختار Tasks و Keep و Mail و Calendar و Google Chat، صاوب التصدير وحمل الفيشي ‎.zip، ومن بعد ختارو هنا. كل منتوج كيولي خط سباحة: البريد للعرض Email، ليستات المهام والملاحظات مع قوائم التدقيق ديالهم، أحداث التقويم والمهام بالتواريخ، وفضاءات الدردشة اللي الرسائل ديالها كيوليو تعليقات للعرض Chat. المنتوجات الأخرى والمرفقات ما كيتستوردوش.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "فـ Telegram Desktop، حل Settings، Advanced، Export Telegram data، ختار الصيغة JSON وصدر، ومن بعد ختار الفيشي result.json، ولا لصق النص ديالو. كل دردشة كتولي بطاقة فـ Direct messages ولا Groups ولا Channels، والرسائل ديالها كيوليو تعليقات البطاقة، باش العرض Chat يبين الدردشة. التصاور والفيشيات ما كيتستوردوش.",
"import-board-instruction-whatsapp": "فـ WhatsApp، حل الدردشة، ختار Export chat بلا وسائط، وختار الفيشي ‎.txt هنا، ولا لصق النص ديالو. الدردشة كتولي بطاقة والرسائل ديالها هوما التعليقات ديالها، باسم اللي صيفطهم والوقت، باش العرض Chat يبينها. الوسائط ورسائل النظام ما كيتستوردوش.",
"import-board-instruction-discord": "صدر قناة ديال Discord بـ DiscordChatExporter بالصيغة JSON وختار الفيشي ‎.json، ولا لصق النص ديالو. القناة كتولي بطاقة فالفئة ديالها، والرسائل ديالها كيوليو تعليقات البطاقة، باش العرض Chat يبين القناة. السيرفر كيولي خط السباحة. المرفقات ما كيتستوردوش.",
"import-board-instruction-rocketchat": "ف Rocket.Chat، صدر البيانات ديالك بصيغة JSON ف «My Data» وختار الفيشي ‎.zip اللي كيصيفط ليك، ولا الفيشي ‎.json المصدر ديال غرفة وحدة. كل غرفة كتولي بطاقة والرسائل ديالها كيوليو تعليقات البطاقة، باش العرض Chat يبين الغرفة. والفيشي ‎.zip اللي كيصدرو WeKan للمستورد CSV ديال Rocket.Chat كيتقرا حتى هو.",
"import-board-instruction-evernote": "فـ Evernote، صدر الملاحظات ولا دفتر كفيشي ‎.enex وختارو هنا، ولا لصق النص ديالو. كل ملاحظة كتولي بطاقة بالنص ديالها، والمربعات ديال المهام كقائمة تدقيق، والوسوم ديالها كعلامات، والتذكير ديالها كتاريخ الاستحقاق؛ والملاحظات اللي التذكير ديالها سالا كيمشيو لـ Done. التصاور والفيشيات المرفقة ما كيتستوردوش.",
"tool-group-kanban": "أدوات كانبان والمشاريع",
"tool-group-issues": "تتبع المشاكل والتحكم فالنسخ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-ত প্ৰকল্পৰ Issues খোলক, তালিকাৰ তলত Also available in: CSV বাছক, স্তম্ভসমূহ বাছক (All columns, Description-ৰ সৈতে) আৰু ৰপ্তানি কৰক, তাৰ পিছত CSV পেষ্ট কৰক। Redmine-এ স্তম্ভসমূহৰ নাম আপোনাৰ ভাষাত দিয়ে, গতিকে ৰপ্তানি কৰাৰ আগতে My account-ত আপোনাৰ ভাষা ইংৰাজী কৰক। প্ৰতিটো স্থিতি এটা তালিকা হয় আৰু সমস্যাসমূহ কাৰ্ড হয়, ট্ৰেকাৰক লেবেল হিচাপে, দায়িত্বপ্ৰাপ্ত, লেখক, তাৰিখ, অভিভাৱক কাম আৰু সম্পৰ্কিত সমস্যাৰ সৈতে; অগ্ৰাধিকাৰ, শ্ৰেণী, লক্ষ্য সংস্কৰণ, অনুমানিক সময়, % Done আৰু কাষ্টম ক্ষেত্ৰসমূহ কাষ্টম ক্ষেত্ৰ হয়।",
"import-board-instruction-notion": "Notion-ত ডাটাবেছটো সম্পূৰ্ণ পৃষ্ঠা হিচাপে খোলক, ••• আৰু Export বাছক, Markdown & CSV বাছক, আৰু ই ডাউনলোড কৰা .zip ফাইলটো, বা তাৰ পৰা এটা ডাটাবেছ CSV বাছক, বা সেই CSV পেষ্ট কৰক। Status নামৰ স্তম্ভ তালিকা হয় (নাথাকিলে, select যেন লগা প্ৰথম স্তম্ভটো হয়, আৰু আমদানি প্ৰতিবেদনে কোনটো কয়); শাৰীসমূহ সিহঁতৰ শিৰোনাম, টেগক লেবেল হিচাপে, মানুহক সদস্য হিচাপে, তাৰিখ, আৰু পৃষ্ঠাৰ পাঠক বিৱৰণ হিচাপে লৈ কাৰ্ড হয়; অন্য স্তম্ভসমূহ কাষ্টম ক্ষেত্ৰ হয়। সম্পৰ্ক, ছবি আৰু সংলগ্নসমূহ আমদানি কৰা নহয়।",
"import-board-instruction-plane": "Plane-ত Workspace Settings খোলক, Exports বাছক, প্ৰকল্পসমূহ JSON, CSV বা Excel হিচাপে ৰপ্তানি কৰক আৰু .zip ফাইলটো ডাউনলোড কৰক, তাৰ পিছত সেই ফাইলটো, বা ইয়াৰ ভিতৰৰ এটা ফাইল বাছক, বা JSON বা CSV পেষ্ট কৰক। অৱস্থাসমূহ তালিকা হয়, প্ৰকল্পসমূহ পথ হয়, আৰু সমস্যাসমূহ সিহঁতৰ চিনাক্তকাৰী, অভিভাৱক, দায়িত্বপ্ৰাপ্ত, লেবেল, তাৰিখ, লিংক আৰু মন্তব্যৰ সৈতে কাৰ্ড হয়; অগ্ৰাধিকাৰ, অনুমান, চক্ৰ আৰু মডিউল কাষ্টম ক্ষেত্ৰ হয়। Plane-ৰ ৰপ্তানিত কোনো বিৱৰণ বা সংলগ্ন নাথাকে, গতিকে সেইবোৰ আমদানি কৰা নহয়।",
"import-board-instruction-fizzy": "Fizzy-ত, \"Account settings\"-ত একাউণ্টটো ৰপ্তানি কৰক, বা \"Download my data\"-ৰে আপোনাৰ নিজৰ কাৰ্ডবোৰ, আৰু Fizzy-এ আপোনালৈ পঠোৱা .zip ফাইলটো, বা এখন কাৰ্ডৰ .json ফাইলটো বাছক। ফলকবোৰ পথ হয় আৰু স্তম্ভবোৰ তালিকা হয়, \"Maybe?\", \"Not now\" আৰু \"Done\" Fizzy-ৰ দৰেই থাকে; কাৰ্ডবোৰে সিহঁতৰ বিৱৰণ, লেবেল, দায়িত্বপ্ৰাপ্ত ব্যক্তি, পৰীক্ষা তালিকা হিচাপে পদক্ষেপ, মন্তব্য আৰু ফাইল ৰাখে।",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt বা Gmail-এ Google Takeout-ৰ জৰিয়তে সংৰক্ষণ কৰাৰ দৰে এটা .mbox ফাইল, বা এটা অকলশৰীয়া .eml বাৰ্তা বাছক, বা ইয়াৰ পাঠ পেষ্ট কৰক। প্ৰতিটো কথোপকথন ইয়াৰ প্ৰেৰক, প্ৰাপক আৰু বিষয়ৰ সৈতে Inbox তালিকাত এখন কাৰ্ড হয়, যাতে ই Email দৃশ্যত দেখা যায়; উত্তৰবোৰ ইয়াৰ মন্তব্য হয়। Gmail লেবেলবোৰ লেবেল হয়। সংলগ্নীবোৰ আমদানি কৰা নহয়।",
"import-board-instruction-ical": "Google Calendar, Apple Calendar বা Reminders, Thunderbird, Nextcloud বা Outlook-এ ৰপ্তানি কৰাৰ দৰে এটা .ics দিনপঞ্জী ফাইল বাছক, বা ইয়াৰ পাঠ পেষ্ট কৰক। কামবোৰ সিহঁতৰ স্থিতি অনুসৰি To Do, In Progress, Done বা Cancelled-লৈ যায়, আৰু অনুষ্ঠানবোৰ Events-লৈ, সিহঁতৰ আৰম্ভণি আৰু নিৰ্ধাৰিত তাৰিখৰ সৈতে, যাতে সেইবোৰ Calendar আৰু Gantt দৃশ্যত দেখা যায়। শ্ৰেণী আৰু অগ্ৰাধিকাৰ লেবেল হয়। পুনৰাবৃত্ত বস্তুবোৰ এবাৰহে আমদানি কৰা হয়।",
"import-board-instruction-googletakeout": "takeout.google.com-ত Tasks, Keep, Mail, Calendar আৰু Google Chat বাছক, ৰপ্তানি সৃষ্টি কৰক আৰু .zip ফাইলটো ডাউনলোড কৰক, তাৰ পিছত ইয়াত বাছক। প্ৰতিটো সামগ্ৰী এটা পথ হয়: Email দৃশ্যৰ বাবে মেইল, পৰীক্ষা তালিকাৰ সৈতে কামৰ তালিকা আৰু টোকা, তাৰিখৰ সৈতে দিনপঞ্জীৰ অনুষ্ঠান আৰু কাম, আৰু চেট স্থান যাৰ বাৰ্তাবোৰ Chat দৃশ্যৰ বাবে মন্তব্য। অন্য সামগ্ৰী আৰু সংলগ্নীবোৰ আমদানি কৰা নহয়।",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-ত Settings, Advanced, Export Telegram data খোলক, JSON ফৰ্মেট বাছি ৰপ্তানি কৰক, তাৰ পিছত result.json ফাইলটো বাছক, বা ইয়াৰ পাঠ পেষ্ট কৰক। প্ৰতিটো চেট Direct messages, Groups বা Channels-ত এখন কাৰ্ড হয়, আৰু ইয়াৰ বাৰ্তাবোৰ কাৰ্ডৰ মন্তব্য হয়, যাতে Chat দৃশ্যই চেটটো দেখুৱায়। ফটো আৰু ফাইলবোৰ আমদানি কৰা নহয়।",
"import-board-instruction-whatsapp": "WhatsApp-ত চেটটো খোলক, মিডিয়া অবিহনে Export chat বাছক, আৰু .txt ফাইলটো ইয়াত বাছক, বা ইয়াৰ পাঠ পেষ্ট কৰক। চেটটো এখন কাৰ্ড হয় যাৰ বাৰ্তাবোৰ, প্ৰেৰক আৰু সময় অনুসৰি, ইয়াৰ মন্তব্য, যাতে Chat দৃশ্যই ইয়াক দেখুৱায়। মিডিয়া আৰু ছিষ্টেম বাৰ্তাবোৰ আমদানি কৰা নহয়।",
"import-board-instruction-discord": "DiscordChatExporter-ৰে JSON ফৰ্মেটত এটা Discord চেনেল ৰপ্তানি কৰক আৰু .json ফাইলটো বাছক, বা ইয়াৰ পাঠ পেষ্ট কৰক। চেনেলটো ইয়াৰ শ্ৰেণীত এখন কাৰ্ড হয়, আৰু ইয়াৰ বাৰ্তাবোৰ কাৰ্ডৰ মন্তব্য হয়, যাতে Chat দৃশ্যই চেনেলটো দেখুৱায়। ছাৰ্ভাৰটো পথ হয়। সংলগ্নীবোৰ আমদানি কৰা নহয়।",
"import-board-instruction-rocketchat": "Rocket.Chat-ত, \"My Data\"-ত আপোনাৰ ডাটা JSON হিচাপে ৰপ্তানি কৰক আৰু ই আপোনালৈ পঠোৱা .zip ফাইলটো, বা এটা ৰুমৰ ৰপ্তানি কৰা .json ফাইলটো বাছক। প্ৰতিটো ৰুম এখন কাৰ্ড হয় আৰু ইয়াৰ বাৰ্তাবোৰ কাৰ্ডৰ মন্তব্য হয়, যাতে Chat দৃশ্যই ৰুমটো দেখুৱায়। Rocket.Chat-ৰ CSV আমদানিকাৰীৰ বাবে WeKan-এ ৰপ্তানি কৰা .zip-টোও পঢ়া হয়।",
"import-board-instruction-evernote": "Evernote-ত টোকাবোৰ বা এখন টোকাবহী .enex ফাইল হিচাপে ৰপ্তানি কৰক আৰু ইয়াত বাছক, বা ইয়াৰ পাঠ পেষ্ট কৰক। প্ৰতিটো টোকা ইয়াৰ পাঠ, পৰীক্ষা তালিকা হিচাপে ইয়াৰ কৰিবলগীয়া বাকচ, লেবেল হিচাপে ইয়াৰ টেগ আৰু নিৰ্ধাৰিত তাৰিখ হিচাপে ইয়াৰ সোঁৱৰণীৰ সৈতে এখন কাৰ্ড হয়; যিবোৰ টোকাৰ সোঁৱৰণী সম্পূৰ্ণ সেইবোৰ Done-লৈ যায়। ছবি আৰু সংলগ্ন ফাইলবোৰ আমদানি কৰা নহয়।",
"tool-group-kanban": "কানবান আৰু প্ৰকল্প সঁজুলি",
"tool-group-issues": "সমস্যা অনুসৰণকাৰী আৰু সংস্কৰণ নিয়ন্ত্ৰণ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "En Redmine, abri les Issues del proyeutu, escueyi Also available in: CSV embaxo de la llista, escueyi les columnes (All columns, con Description) y esporta, dempués apega'l CSV. Redmine nome les columnes na to llingua, asina que pon la to llingua n'inglés en My account enantes d'esportar. Cada estáu conviértese nuna llista y les incidencies en tarxetes, col tracker como etiqueta, persona asignada, autor, feches, xera madre y incidencies rellacionaes; la prioridá, categoría, versión oxetivu, tiempu estimáu, % Done y los campos personalizaos conviértense en campos personalizaos.",
"import-board-instruction-notion": "En Notion, abri la base de datos como páxina completa, escueyi ••• y Export, escueyi Markdown & CSV, y escueyi'l ficheru .zip que se descarga, o un CSV de base de datos de dientro, o apega esi CSV. Una columna llamada Status conviértese nes llistes (ensin ella, failo la primer columna que paeza una seleición, y l'informe d'importación diz cuála); les fileres conviértense en tarxetes col so títulu, etiquetes, persones como miembros, feches, y el testu de la páxina como descripción; les otres columnes conviértense en campos personalizaos. Les rellaciones, imáxenes y axuntos nun s'importen.",
"import-board-instruction-plane": "En Plane, abri Workspace Settings, escueyi Exports, esporta los proyeutos como JSON, CSV o Excel y descarga'l ficheru .zip, dempués escueyi esi ficheru, o un ficheru de dientro, o apega'l JSON o'l CSV. Los estaos conviértense en llistes, los proyeutos en carriles, y les incidencies en tarxetes col so identificador, madre, persones asignaes, etiquetes, feches, enllaces y comentarios; la prioridá, estimación, ciclu y módulu conviértense en campos personalizaos. La esportación de Plane nun tien descripciones nin axuntos, asina que nun s'importen.",
"import-board-instruction-fizzy": "En Fizzy, esporta la cuenta en «Account settings», o les tos tarxetes con «Download my data», y escueyi'l ficheru .zip que te unvia Fizzy, o'l ficheru .json d'una tarxeta. Los tableros conviértense en carriles y les columnes en llistes, con «Maybe?», «Not now» y «Done» como en Fizzy; les tarxetes conserven la so descripción, etiquetes, asignaos, pasos como llista de verificación, comentarios y ficheros.",
"import-board-instruction-mail": "Escueyi un ficheru .mbox, como lu guarden Thunderbird, Apple Mail, mutt o Gmail per Google Takeout, o un solu mensaxe .eml, o apega'l so testu. Cada conversación conviértese nuna tarxeta na llista Inbox, col so remitente, destinatarios y asuntu, pa que s'amuese na vista Email; les rempuestes conviértense nos sos comentarios. Les etiquetes de Gmail conviértense n'etiquetes. Los axuntos nun s'importen.",
"import-board-instruction-ical": "Escueyi un ficheru de calendariu .ics, como lu esporten Google Calendar, Apple Calendar o Reminders, Thunderbird, Nextcloud o Outlook, o apega'l so testu. Les xeres van a To Do, In Progress, Done o Cancelled según el so estáu, y los eventos a Events, coles sos feches d'aniciu y de vencimientu, pa que s'amuesen nes vistes Calendar y Gantt. Les categoríes y la prioridá conviértense n'etiquetes. Los elementos que se repiten impórtense una vegada.",
"import-board-instruction-googletakeout": "En takeout.google.com, escueyi Tasks, Keep, Mail, Calendar y Google Chat, crea la esportación y descarga'l ficheru .zip, dempués escuéyilu equí. Cada productu conviértese nun carril: el corréu pa la vista Email, les llistes de xeres y les notes coles sos llistes de verificación, los eventos de calendariu y les xeres con feches, y los espacios de chat que los sos mensaxes son comentarios pa la vista Chat. Otros productos y los axuntos nun s'importen.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "En Telegram Desktop, abri Settings, Advanced, Export Telegram data, escueyi'l formatu JSON y esporta, dempués escueyi'l ficheru result.json, o apega'l so testu. Cada chat conviértese nuna tarxeta en Direct messages, Groups o Channels, y los sos mensaxes conviértense nos comentarios de la tarxeta, pa que la vista Chat amuese'l chat. Les semeyes y los ficheros nun s'importen.",
"import-board-instruction-whatsapp": "En WhatsApp, abri'l chat, escueyi Export chat ensin multimedia, y escueyi equí'l ficheru .txt, o apega'l so testu. El chat conviértese nuna tarxeta que los sos mensaxes son los sos comentarios, pol so remitente y hora, pa que la vista Chat lu amuese. La multimedia y los mensaxes del sistema nun s'importen.",
"import-board-instruction-discord": "Esporta una canal de Discord con DiscordChatExporter nel formatu JSON y escueyi'l ficheru .json, o apega'l so testu. La canal conviértese nuna tarxeta na so categoría, y los sos mensaxes conviértense nos comentarios de la tarxeta, pa que la vista Chat amuese la canal. El sirvidor conviértese nel carril. Los axuntos nun s'importen.",
"import-board-instruction-rocketchat": "En Rocket.Chat, esporta los tos datos como JSON en «My Data» y escueyi'l ficheru .zip que te unvia, o'l ficheru .json esportáu d'una sala. Cada sala conviértese nuna tarxeta y los sos mensaxes conviértense nos comentarios de la tarxeta, pa que la vista Chat amuese la sala. Tamién se llee'l .zip que WeKan esporta pal importador CSV de Rocket.Chat.",
"import-board-instruction-evernote": "En Evernote, esporta les notes o un cuadernu como ficheru .enex y escuéyilu equí, o apega'l so testu. Cada nota conviértese nuna tarxeta col so testu, les sos caxelles de xeres como llista de verificación, les sos etiquetes como etiquetes y el so recordatoriu como fecha de vencimientu; les notes que'l so recordatoriu ta fechu van a Done. Les imáxenes y los ficheros axuntos nun s'importen.",
"tool-group-kanban": "Ferramientes Kanban y de proyeutos",
"tool-group-issues": "Seguimientu d'incidencies y control de versiones",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine ukan, proyecto Issues jist'araña, listan aynacht'ap Also available in: CSV ajlliña, columnanak ajlliña (All columns, Description ukamp chika) ukat mistuyaña, ukat CSV qillqaqaña. Redmine ukax columnanak arumaruw sutichi, ukhamax mistuyañat nayraqat My account ukan arum inglés aruru uchaña. Sapa estado mä listaruw tuku, issues ukanakax tarjetanakaruw tuku, tracker chimpujama, lurayiri, qillqiri, urunaka, awki lurawi ukat chikt'ata issues ukanakamp chika; nayrïr lurañ, categoría, target version, estimated time, % Done ukat pachpa camponakax pachpa camponakaruw tuku.",
"import-board-instruction-notion": "Notion ukan, base de datos taqpach pankjama jist'araña, ••• ukat Export ajlliña, Markdown & CSV ajlliña, ukat apaqki uka .zip qillqat ajlliña, jan ukax ukat mä base de datos CSV, jan ukax uka CSV qillqaqaña. Status sutini columnax listanakaruw tuku (jan utjki ukhax, select ukar uñtasit nayrïr columnaw tuku, apaniñ yatiyäwix kawkïris sasaw qhanañchi); siqinakax tarjetanakaruw tuku sutipamp, chimpunakapamp, jaqinakax masinakjama, urunaka, panka qillqax qhanañchäwjama; yaqha columnanakax pachpa camponakaruw tuku. Relaciones, uñnaqanaka ukat chikachatanakax janiw apanitäkiti.",
"import-board-instruction-plane": "Plane ukan, Workspace Settings jist'araña, Exports ajlliña, proyectonak JSON, CSV jan ukax Excel ukham mistuyaña ukat .zip qillqat apaqaña, ukat uka qillqat ajlliña, jan ukax manqhapan mä qillqat, jan ukax JSON jan ukax CSV qillqaqaña. Estados ukanakax listanakaruw tuku, proyectonakax thakhinakaruw tuku, issues ukanakax tarjetanakaruw tuku identificador, awki, lurayirinaka, chimpunaka, urunaka, chinunaka ukat amuyt'awinakapamp chika; nayrïr lurañ, estimate, ciclo ukat módulo ukanakax pachpa camponakaruw tuku. Plane mistuyäwipanx janiw qhanañchäwinakas chikachatanakas utjkiti, ukhamax janiw apanitäkiti.",
"import-board-instruction-fizzy": "Fizzy ukanxa, cuenta \"Account settings\" ukan anqäxar apayaña, jan ukax juman kartanakam \"Download my data\" ukampi, ukat Fizzy jumar apayki uka .zip qillqat wayaq ajlliña, jan ukax mä kartan .json qillqat wayaqapa. Pirqanakax thakhinakaruw tukupxi, columnanakax sutinakaruw tukupxi, \"Maybe?\", \"Not now\" ukat \"Done\" Fizzy ukankir kikiwa; kartanakax qhananchawipa, unanchanakapa, lurañataki churatanaka, kayunak uñakipaña sutinakjama, arxatanaka ukat qillqat wayaqanak katxapxi.",
"import-board-instruction-mail": "Mä .mbox qillqat wayaq ajlliña, kunjamtix Thunderbird, Apple Mail, mutt jan ukax Gmail Google Takeout tuqi imapki ukhama, jan ukax mä sapa .eml yatiyawi, jan ukax qillqap ucharaña. Sapa aruskipawix Inbox sutinakan mä kartaru tukuspa, apayirimpi, katuqirinakampi, yatiyawi sutipampi, ukhamat Email uñjañan uñstañapataki; kutt'ayawinakax arxatanakaparuw tukupxi. Gmail unanchanakax unanchanakaruw tukupxi. Chikt'atanakax janiw apsutäkiti.",
"import-board-instruction-ical": "Mä .ics almanaq qillqat wayaq ajlliña, kunjamtix Google Calendar, Apple Calendar jan ukax Reminders, Thunderbird, Nextcloud jan ukax Outlook anqäxar apayapki ukhama, jan ukax qillqap ucharaña. Lurawinakax To Do, In Progress, Done jan ukax Cancelled ukaruw sarapxi kunjamäkisa ukarjama, ukat lurawi urunakax Events ukaru, qalltaw urumpi tukuyañ urumpi, ukhamat Calendar ukat Gantt uñjañanakan uñstañapataki. Kasta ukat nayrir chiqawix unanchanakaruw tukupxi. Kutt'ir yänakax mä kutikiw apsutäpxi.",
"import-board-instruction-googletakeout": "takeout.google.com ukanx Tasks, Keep, Mail, Calendar ukat Google Chat ajlliña, anqäxar apayañ luraña ukat .zip qillqat wayaq apaqaña, ukatsti akan ajlliña. Sapa yänakax mä thakhiruw tukuspa: Email uñjañatakix qillqanaka, lurawi sutinakampi qillqanakampi uñakipaña sutinakapampi, almanaq lurawinaka ukat lurawinaka urunakampi, ukat aruskipañ chiqanaka, yatiyawinakapax Chat uñjañatakix arxatanakawa. Yaqha yänakampi chikt'atanakampix janiw apsutäkiti.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop ukanx Settings, Advanced, Export Telegram data jist'araña, JSON uñnaqa ajlliña ukat anqäxar apayaña, ukatsti result.json qillqat wayaq ajlliña, jan ukax qillqap ucharaña. Sapa aruskipawix Direct messages, Groups jan ukax Channels ukan mä kartaru tukuspa, yatiyawinakapax kartan arxatanakaparuw tukupxi, ukhamat Chat uñjañax aruskipaw uñacht'ayañapataki. Jamuqanakampi qillqat wayaqanakampix janiw apsutäkiti.",
"import-board-instruction-whatsapp": "WhatsApp ukanx aruskipaw jist'araña, Export chat media janiw ajlliña, ukat .txt qillqat wayaq akan ajlliña, jan ukax qillqap ucharaña. Aruskipawix mä kartaruw tukuspa, yatiyawinakapax arxatanakapawa, apayiripar pachaparjama, ukhamat Chat uñjañax uñacht'ayañapataki. Media ukat sistema yatiyawinakax janiw apsutäkiti.",
"import-board-instruction-discord": "Mä Discord kanal DiscordChatExporter ukampi JSON uñnaqan anqäxar apayaña ukat .json qillqat wayaq ajlliña, jan ukax qillqap ucharaña. Kanalax kastapan mä kartaruw tukuspa, yatiyawinakapax kartan arxatanakaparuw tukupxi, ukhamat Chat uñjañax kanal uñacht'ayañapataki. Servidorax thakhiruw tukuspa. Chikt'atanakax janiw apsutäkiti.",
"import-board-instruction-rocketchat": "Rocket.Chat ukanxa, yatiyawinakam JSON uñnaqan \"My Data\" ukan anqäxar apayaña ukat jumar apayki uka .zip qillqat wayaq ajlliña, jan ukax mä utan anqäxar apayat .json qillqat wayaqapa. Sapa utax mä kartaruw tukuspa, yatiyawinakapax kartan arxatanakaparuw tukupxi, ukhamat Chat uñjañax uta uñacht'ayañapataki. WeKan ukax Rocket.Chat ukan CSV apsurip layku anqäxar apayki uka .zip ukax ullatarakiwa.",
"import-board-instruction-evernote": "Evernote ukanx qillqanaka jan ukax mä qillqañ panka .enex qillqat wayaq ukham anqäxar apayaña ukat akan ajlliña, jan ukax qillqap ucharaña. Sapa qillqax mä kartaruw tukuspa qillqapampi, lurañ cajanakapax uñakipaña sutjama, tags ukanakapax unanchanakjama ukat amtayawipax tukuyañ urjama; amtayawipax tukuyatäki uka qillqanakax Done ukaruw sarapxi. Jamuqanakampi chikt'at qillqat wayaqanakampix janiw apsutäkiti.",
"tool-group-kanban": "Kanban ukat proyecto irnaqañanaka",
"tool-group-issues": "Jan walt'awinak arkañanaka ukat versión uñjaña",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-da layihənin Issues bölməsini açın, siyahının aşağısında Also available in: CSV seçin, sütunları seçib (All columns, Description ilə) ixrac edin, sonra CSV-ni yapışdırın. Redmine sütunları sizin dilinizdə adlandırır, buna görə ixracdan əvvəl My account bölməsində dili English edin. Hər status siyahıya, məsələlər isə etiketə çevrilən izləyici növü, təyin edilmiş şəxs, müəllif, tarixlər, ana tapşırıq və əlaqəli məsələlər ilə kartlara çevrilir; prioritet, kateqoriya, hədəf versiya, təxmini vaxt, % Done və fərdi sahələr fərdi sahələrə çevrilir.",
"import-board-instruction-notion": "Notion-da verilənlər bazasını tam səhifə kimi açın, ••• və Export seçin, Markdown & CSV seçin və endirilən .zip faylını və ya içindəki bir verilənlər bazası CSV-sini seçin, yaxud həmin CSV-ni yapışdırın. Status adlı sütun siyahılara çevrilir (beləsi yoxdursa, seçim sahəsinə bənzəyən ilk sütun istifadə edilir və idxal hesabatında hansı olduğu göstərilir); sətirlər başlıqları, etiketləri, üzvlərə çevrilən şəxsləri, tarixləri və təsvirə çevrilən səhifə mətni ilə kartlara çevrilir; digər sütunlar fərdi sahələrə çevrilir. Əlaqələr, şəkillər və qoşmalar idxal edilmir.",
"import-board-instruction-plane": "Plane-də Workspace Settings bölməsini açın, Exports seçin, layihələri JSON, CSV və ya Excel kimi ixrac edib .zip faylını endirin, sonra həmin faylı və ya içindən bir faylı seçin, yaxud JSON və ya CSV-ni yapışdırın. Vəziyyətlər siyahılara, layihələr üzgüçülük zolaqlarına, məsələlər isə identifikatorları, ana elementləri, təyin edilmiş şəxsləri, etiketləri, tarixləri, keçidləri və şərhləri ilə kartlara çevrilir; prioritet, təxmin, dövr və modul fərdi sahələrə çevrilir. Plane ixracında təsvirlər və qoşmalar yoxdur, buna görə onlar idxal edilmir.",
"import-board-instruction-fizzy": "Fizzy-də hesabı \"Account settings\" bölməsində, yaxud öz kartlarınızı \"Download my data\" ilə ixrac edin və Fizzy-nin sizə göndərdiyi .zip faylını, yaxud bir kartın .json faylını seçin. Lövhələr zolaqlar, sütunlar isə siyahılar olur, \"Maybe?\", \"Not now\" və \"Done\" Fizzy-dəki kimi qalır; kartlar təsvirini, etiketlərini, təyin edilmiş şəxsləri, addımları yoxlama siyahısı kimi, şərhləri və faylları saxlayır.",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt və ya Google Takeout vasitəsilə Gmail-in saxladığı kimi .mbox faylı, və ya tək .eml mesajı seçin, yaxud onun mətnini yapışdırın. Hər söhbət göndərəni, alıcıları və mövzusu ilə Inbox siyahısında bir kart olur ki, Email görünüşündə görünsün; cavablar onun şərhləri olur. Gmail etiketləri etiketlər olur. Qoşmalar idxal edilmir.",
"import-board-instruction-ical": "Google Calendar, Apple Calendar və ya Reminders, Thunderbird, Nextcloud və ya Outlook-un ixrac etdiyi kimi .ics təqvim faylı seçin, yaxud onun mətnini yapışdırın. Tapşırıqlar statuslarına görə To Do, In Progress, Done və ya Cancelled siyahısına, hadisələr isə Events siyahısına başlanğıc və son tarixləri ilə gedir ki, Calendar və Gantt görünüşlərində görünsünlər. Kateqoriyalar və prioritet etiketlər olur. Təkrarlanan elementlər bir dəfə idxal edilir.",
"import-board-instruction-googletakeout": "takeout.google.com saytında Tasks, Keep, Mail, Calendar və Google Chat seçin, ixracı yaradın və .zip faylını endirin, sonra onu burada seçin. Hər məhsul bir zolaq olur: Email görünüşü üçün poçt, yoxlama siyahıları ilə tapşırıq siyahıları və qeydlər, tarixləri ilə təqvim hadisələri və tapşırıqlar, və mesajları Chat görünüşü üçün şərhlər olan söhbət məkanları. Digər məhsullar və qoşmalar idxal edilmir.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-da Settings, Advanced, Export Telegram data açın, JSON formatını seçib ixrac edin, sonra result.json faylını seçin, yaxud onun mətnini yapışdırın. Hər söhbət Direct messages, Groups və ya Channels-da bir kart olur, onun mesajları kartın şərhləri olur ki, Chat görünüşü söhbəti göstərsin. Şəkillər və fayllar idxal edilmir.",
"import-board-instruction-whatsapp": "WhatsApp-da söhbəti açın, mediasız Export chat seçin və .txt faylını burada seçin, yaxud onun mətnini yapışdırın. Söhbət mesajları göndərənə və vaxta görə onun şərhləri olan bir kart olur ki, Chat görünüşü onu göstərsin. Media və sistem mesajları idxal edilmir.",
"import-board-instruction-discord": "Discord kanalını DiscordChatExporter ilə JSON formatında ixrac edin və .json faylını seçin, yaxud onun mətnini yapışdırın. Kanal öz kateqoriyasında bir kart olur, onun mesajları kartın şərhləri olur ki, Chat görünüşü kanalı göstərsin. Server zolaq olur. Qoşmalar idxal edilmir.",
"import-board-instruction-rocketchat": "Rocket.Chat-də məlumatlarınızı \"My Data\" bölməsində JSON kimi ixrac edin və onun sizə göndərdiyi .zip faylını, yaxud bir otağın ixrac edilmiş .json faylını seçin. Hər otaq bir kart olur, onun mesajları isə kartın şərhləri olur ki, Chat görünüşü otağı göstərsin. WeKan-ın Rocket.Chat-in CSV idxalçısı üçün ixrac etdiyi .zip də oxunur.",
"import-board-instruction-evernote": "Evernote-da qeydləri və ya bir qeyd dəftərini .enex faylı kimi ixrac edin və onu burada seçin, yaxud onun mətnini yapışdırın. Hər qeyd mətni, yoxlama siyahısı kimi tapşırıq qutuları, etiketlər kimi teqləri və son tarix kimi xatırlatması ilə bir kart olur; xatırlatması tamamlanmış qeydlər Done siyahısına gedir. Şəkillər və qoşulmuş fayllar idxal edilmir.",
"tool-group-kanban": "Kanban və layihə alətləri",
"tool-group-issues": "Problem izləyiciləri və versiya nəzarəti",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-da layihənin Issues bölməsini açın, siyahının aşağısında Also available in: CSV seçin, sütunları seçib (All columns, Description ilə) ixrac edin, sonra CSV-ni yapışdırın. Redmine sütunları sizin dilinizdə adlandırır, buna görə ixracdan əvvəl My account bölməsində dili English edin. Hər status siyahıya, məsələlər isə etiketə çevrilən izləyici növü, təyin edilmiş şəxs, müəllif, tarixlər, ana tapşırıq və əlaqəli məsələlər ilə kartlara çevrilir; prioritet, kateqoriya, hədəf versiya, təxmini vaxt, % Done və fərdi sahələr fərdi sahələrə çevrilir.",
"import-board-instruction-notion": "Notion-da verilənlər bazasını tam səhifə kimi açın, ••• və Export seçin, Markdown & CSV seçin və endirilən .zip faylını və ya içindəki bir verilənlər bazası CSV-sini seçin, yaxud həmin CSV-ni yapışdırın. Status adlı sütun siyahılara çevrilir (beləsi yoxdursa, seçim sahəsinə bənzəyən ilk sütun istifadə edilir və idxal hesabatında hansı olduğu göstərilir); sətirlər başlıqları, etiketləri, üzvlərə çevrilən şəxsləri, tarixləri və təsvirə çevrilən səhifə mətni ilə kartlara çevrilir; digər sütunlar fərdi sahələrə çevrilir. Əlaqələr, şəkillər və qoşmalar idxal edilmir.",
"import-board-instruction-plane": "Plane-də Workspace Settings bölməsini açın, Exports seçin, layihələri JSON, CSV və ya Excel kimi ixrac edib .zip faylını endirin, sonra həmin faylı və ya içindən bir faylı seçin, yaxud JSON və ya CSV-ni yapışdırın. Vəziyyətlər siyahılara, layihələr üzgüçülük zolaqlarına, məsələlər isə identifikatorları, ana elementləri, təyin edilmiş şəxsləri, etiketləri, tarixləri, keçidləri və şərhləri ilə kartlara çevrilir; prioritet, təxmin, dövr və modul fərdi sahələrə çevrilir. Plane ixracında təsvirlər və qoşmalar yoxdur, buna görə onlar idxal edilmir.",
"import-board-instruction-fizzy": "Fizzy-də hesabı \"Account settings\" bölməsində, yaxud öz kartlarınızı \"Download my data\" ilə ixrac edin və Fizzy-nin sizə göndərdiyi .zip faylını, yaxud bir kartın .json faylını seçin. Lövhələr zolaqlar, sütunlar isə siyahılar olur, \"Maybe?\", \"Not now\" və \"Done\" Fizzy-dəki kimi qalır; kartlar təsvirini, etiketlərini, təyin edilmiş şəxsləri, addımları yoxlama siyahısı kimi, şərhləri və faylları saxlayır.",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt və ya Google Takeout vasitəsilə Gmail-in saxladığı kimi .mbox faylı, və ya tək .eml mesajı seçin, yaxud onun mətnini yapışdırın. Hər söhbət göndərəni, alıcıları və mövzusu ilə Inbox siyahısında bir kart olur ki, Email görünüşündə görünsün; cavablar onun şərhləri olur. Gmail etiketləri etiketlər olur. Qoşmalar idxal edilmir.",
"import-board-instruction-ical": "Google Calendar, Apple Calendar və ya Reminders, Thunderbird, Nextcloud və ya Outlook-un ixrac etdiyi kimi .ics təqvim faylı seçin, yaxud onun mətnini yapışdırın. Tapşırıqlar statuslarına görə To Do, In Progress, Done və ya Cancelled siyahısına, hadisələr isə Events siyahısına başlanğıc və son tarixləri ilə gedir ki, Calendar və Gantt görünüşlərində görünsünlər. Kateqoriyalar və prioritet etiketlər olur. Təkrarlanan elementlər bir dəfə idxal edilir.",
"import-board-instruction-googletakeout": "takeout.google.com saytında Tasks, Keep, Mail, Calendar və Google Chat seçin, ixracı yaradın və .zip faylını endirin, sonra onu burada seçin. Hər məhsul bir zolaq olur: Email görünüşü üçün poçt, yoxlama siyahıları ilə tapşırıq siyahıları və qeydlər, tarixləri ilə təqvim hadisələri və tapşırıqlar, və mesajları Chat görünüşü üçün şərhlər olan söhbət məkanları. Digər məhsullar və qoşmalar idxal edilmir.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-da Settings, Advanced, Export Telegram data açın, JSON formatını seçib ixrac edin, sonra result.json faylını seçin, yaxud onun mətnini yapışdırın. Hər söhbət Direct messages, Groups və ya Channels-da bir kart olur, onun mesajları kartın şərhləri olur ki, Chat görünüşü söhbəti göstərsin. Şəkillər və fayllar idxal edilmir.",
"import-board-instruction-whatsapp": "WhatsApp-da söhbəti açın, mediasız Export chat seçin və .txt faylını burada seçin, yaxud onun mətnini yapışdırın. Söhbət mesajları göndərənə və vaxta görə onun şərhləri olan bir kart olur ki, Chat görünüşü onu göstərsin. Media və sistem mesajları idxal edilmir.",
"import-board-instruction-discord": "Discord kanalını DiscordChatExporter ilə JSON formatında ixrac edin və .json faylını seçin, yaxud onun mətnini yapışdırın. Kanal öz kateqoriyasında bir kart olur, onun mesajları kartın şərhləri olur ki, Chat görünüşü kanalı göstərsin. Server zolaq olur. Qoşmalar idxal edilmir.",
"import-board-instruction-rocketchat": "Rocket.Chat-də məlumatlarınızı \"My Data\" bölməsində JSON kimi ixrac edin və onun sizə göndərdiyi .zip faylını, yaxud bir otağın ixrac edilmiş .json faylını seçin. Hər otaq bir kart olur, onun mesajları isə kartın şərhləri olur ki, Chat görünüşü otağı göstərsin. WeKan-ın Rocket.Chat-in CSV idxalçısı üçün ixrac etdiyi .zip də oxunur.",
"import-board-instruction-evernote": "Evernote-da qeydləri və ya bir qeyd dəftərini .enex faylı kimi ixrac edin və onu burada seçin, yaxud onun mətnini yapışdırın. Hər qeyd mətni, yoxlama siyahısı kimi tapşırıq qutuları, etiketlər kimi teqləri və son tarix kimi xatırlatması ilə bir kart olur; xatırlatması tamamlanmış qeydlər Done siyahısına gedir. Şəkillər və qoşulmuş fayllar idxal edilmir.",
"tool-group-kanban": "Kanban və layihə alətləri",
"tool-group-issues": "Problem izləyiciləri və versiya nəzarəti",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-da layihənin Issues bölməsini açın, siyahının aşağısında Also available in: CSV seçin, sütunları seçib (All columns, Description ilə) ixrac edin, sonra CSV-ni yapışdırın. Redmine sütunları sizin dilinizdə adlandırır, buna görə ixracdan əvvəl My account bölməsində dili English edin. Hər status siyahıya, məsələlər isə etiketə çevrilən izləyici növü, təyin edilmiş şəxs, müəllif, tarixlər, ana tapşırıq və əlaqəli məsələlər ilə kartlara çevrilir; prioritet, kateqoriya, hədəf versiya, təxmini vaxt, % Done və fərdi sahələr fərdi sahələrə çevrilir.",
"import-board-instruction-notion": "Notion-da verilənlər bazasını tam səhifə kimi açın, ••• və Export seçin, Markdown & CSV seçin və endirilən .zip faylını və ya içindəki bir verilənlər bazası CSV-sini seçin, yaxud həmin CSV-ni yapışdırın. Status adlı sütun siyahılara çevrilir (beləsi yoxdursa, seçim sahəsinə bənzəyən ilk sütun istifadə edilir və idxal hesabatında hansı olduğu göstərilir); sətirlər başlıqları, etiketləri, üzvlərə çevrilən şəxsləri, tarixləri və təsvirə çevrilən səhifə mətni ilə kartlara çevrilir; digər sütunlar fərdi sahələrə çevrilir. Əlaqələr, şəkillər və qoşmalar idxal edilmir.",
"import-board-instruction-plane": "Plane-də Workspace Settings bölməsini açın, Exports seçin, layihələri JSON, CSV və ya Excel kimi ixrac edib .zip faylını endirin, sonra həmin faylı və ya içindən bir faylı seçin, yaxud JSON və ya CSV-ni yapışdırın. Vəziyyətlər siyahılara, layihələr üzgüçülük zolaqlarına, məsələlər isə identifikatorları, ana elementləri, təyin edilmiş şəxsləri, etiketləri, tarixləri, keçidləri və şərhləri ilə kartlara çevrilir; prioritet, təxmin, dövr və modul fərdi sahələrə çevrilir. Plane ixracında təsvirlər və qoşmalar yoxdur, buna görə onlar idxal edilmir.",
"import-board-instruction-fizzy": "Fizzy-də hesabı \"Account settings\" bölməsində, yaxud öz kartlarınızı \"Download my data\" ilə ixrac edin və Fizzy-nin sizə göndərdiyi .zip faylını, yaxud bir kartın .json faylını seçin. Lövhələr zolaqlar, sütunlar isə siyahılar olur, \"Maybe?\", \"Not now\" və \"Done\" Fizzy-dəki kimi qalır; kartlar təsvirini, etiketlərini, təyin edilmiş şəxsləri, addımları yoxlama siyahısı kimi, şərhləri və faylları saxlayır.",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt və ya Google Takeout vasitəsilə Gmail-in saxladığı kimi .mbox faylı, və ya tək .eml mesajı seçin, yaxud onun mətnini yapışdırın. Hər söhbət göndərəni, alıcıları və mövzusu ilə Inbox siyahısında bir kart olur ki, Email görünüşündə görünsün; cavablar onun şərhləri olur. Gmail etiketləri etiketlər olur. Qoşmalar idxal edilmir.",
"import-board-instruction-ical": "Google Calendar, Apple Calendar və ya Reminders, Thunderbird, Nextcloud və ya Outlook-un ixrac etdiyi kimi .ics təqvim faylı seçin, yaxud onun mətnini yapışdırın. Tapşırıqlar statuslarına görə To Do, In Progress, Done və ya Cancelled siyahısına, hadisələr isə Events siyahısına başlanğıc və son tarixləri ilə gedir ki, Calendar və Gantt görünüşlərində görünsünlər. Kateqoriyalar və prioritet etiketlər olur. Təkrarlanan elementlər bir dəfə idxal edilir.",
"import-board-instruction-googletakeout": "takeout.google.com saytında Tasks, Keep, Mail, Calendar və Google Chat seçin, ixracı yaradın və .zip faylını endirin, sonra onu burada seçin. Hər məhsul bir zolaq olur: Email görünüşü üçün poçt, yoxlama siyahıları ilə tapşırıq siyahıları və qeydlər, tarixləri ilə təqvim hadisələri və tapşırıqlar, və mesajları Chat görünüşü üçün şərhlər olan söhbət məkanları. Digər məhsullar və qoşmalar idxal edilmir.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-da Settings, Advanced, Export Telegram data açın, JSON formatını seçib ixrac edin, sonra result.json faylını seçin, yaxud onun mətnini yapışdırın. Hər söhbət Direct messages, Groups və ya Channels-da bir kart olur, onun mesajları kartın şərhləri olur ki, Chat görünüşü söhbəti göstərsin. Şəkillər və fayllar idxal edilmir.",
"import-board-instruction-whatsapp": "WhatsApp-da söhbəti açın, mediasız Export chat seçin və .txt faylını burada seçin, yaxud onun mətnini yapışdırın. Söhbət mesajları göndərənə və vaxta görə onun şərhləri olan bir kart olur ki, Chat görünüşü onu göstərsin. Media və sistem mesajları idxal edilmir.",
"import-board-instruction-discord": "Discord kanalını DiscordChatExporter ilə JSON formatında ixrac edin və .json faylını seçin, yaxud onun mətnini yapışdırın. Kanal öz kateqoriyasında bir kart olur, onun mesajları kartın şərhləri olur ki, Chat görünüşü kanalı göstərsin. Server zolaq olur. Qoşmalar idxal edilmir.",
"import-board-instruction-rocketchat": "Rocket.Chat-də məlumatlarınızı \"My Data\" bölməsində JSON kimi ixrac edin və onun sizə göndərdiyi .zip faylını, yaxud bir otağın ixrac edilmiş .json faylını seçin. Hər otaq bir kart olur, onun mesajları isə kartın şərhləri olur ki, Chat görünüşü otağı göstərsin. WeKan-ın Rocket.Chat-in CSV idxalçısı üçün ixrac etdiyi .zip də oxunur.",
"import-board-instruction-evernote": "Evernote-da qeydləri və ya bir qeyd dəftərini .enex faylı kimi ixrac edin və onu burada seçin, yaxud onun mətnini yapışdırın. Hər qeyd mətni, yoxlama siyahısı kimi tapşırıq qutuları, etiketlər kimi teqləri və son tarix kimi xatırlatması ilə bir kart olur; xatırlatması tamamlanmış qeydlər Done siyahısına gedir. Şəkillər və qoşulmuş fayllar idxal edilmir.",
"tool-group-kanban": "Kanban və layihə alətləri",
"tool-group-issues": "Problem izləyiciləri və versiya nəzarəti",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-да проекттың Issues бүлеген асығыҙ, исемлек аҫтында Also available in: CSV һайлағыҙ, бағаналарҙы һайлағыҙ (All columns, Description менән) һәм экспортлағыҙ, һуңынан CSV-ны ҡуйығыҙ. Redmine бағаналарҙы һеҙҙең телдә атай, шуға күрә экспортлау алдынан My account-та телде инглизсәгә ҡуйығыҙ. Һәр статус исемлеккә, ә мәсьәләләр билдә булараҡ трекер, яуаплы, автор, көндәр, ата-бурыс һәм бәйле мәсьәләләр менән карточкаларға әйләнә; өҫтөнлөк, категория, маҡсатлы версия, баһаланған ваҡыт, % Done һәм махсус ҡырҙар махсус ҡырҙарға әйләнә.",
"import-board-instruction-notion": "Notion-да мәғлүмәттәр базаһын тулы бит итеп асығыҙ, ••• һәм Export һайлағыҙ, Markdown & CSV һайлағыҙ һәм ул йөкләгән .zip файлын, йәки унан бер мәғлүмәттәр базаһы CSV-ын һайлағыҙ, йәки шул CSV-ны ҡуйығыҙ. Status исемле бағана исемлектәргә әйләнә (ул булмаһа, һайлауға оҡшаған беренсе бағана, һәм импорт отчеты ҡайһыһы икәнен әйтә); юлдар исеме, билдәләр булараҡ тегтары, ағзалар булараҡ кешеләре, көндәре һәм тасуирлама булараҡ бит тексы менән карточкаларға әйләнә; башҡа бағаналар махсус ҡырҙарға әйләнә. Бәйләнештәр, һүрәттәр һәм ҡушымталар импортланмай.",
"import-board-instruction-plane": "Plane-да Workspace Settings асығыҙ, Exports һайлағыҙ, проекттарҙы JSON, CSV йәки Excel итеп экспортлағыҙ һәм .zip файлын йөкләгеҙ, һуңынан шул файлды, йәки уның эсендәге бер файлды һайлағыҙ, йәки JSON йәки CSV-ны ҡуйығыҙ. Торош исемлектәргә, проекттар юлдарға, ә мәсьәләләр идентификаторы, атаһы, яуаплылары, билдәләре, көндәре, һылтанмалары һәм аңлатмалары менән карточкаларға әйләнә; өҫтөнлөк, баһа, цикл һәм модуль махсус ҡырҙарға әйләнә. Plane экспортында тасуирламалар һәм ҡушымталар юҡ, шуға күрә улар импортланмай.",
"import-board-instruction-fizzy": "Fizzy-ҙа иҫәп яҙмаһын «Account settings» бүлегендә, йәки үҙ карточкаларығыҙҙы «Download my data» менән экспортлағыҙ һәм Fizzy һеҙгә ебәргән .zip файлын, йәки бер карточканың .json файлын һайлағыҙ. Такталар юлдарға, бағаналар исемлектәргә әйләнә, «Maybe?», «Not now» һәм «Done» Fizzy-ҙағы кеүек ҡала; карточкалар үҙ тасуирламаһын, билдәләрен, яуаплыларын, аҙымдарҙы тикшереү исемлеге итеп, аңлатмаларҙы һәм файлдарҙы һаҡлай.",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt йәки Google Takeout аша Gmail һаҡлаған .mbox файлын, йәки бер .eml хатын һайлағыҙ, йәки уның текстын индерегеҙ. Һәр әңгәмә ебәреүсеһе, алыусылары һәм темаһы менән Inbox исемлегендә бер карточкаға әйләнә, шуға ла Email күренешендә күренә; яуаптар уның аңлатмаларына әйләнә. Gmail билдәләре билдәләргә әйләнә. Ҡушымталар индерелмәй.",
"import-board-instruction-ical": "Google Calendar, Apple Calendar йәки Reminders, Thunderbird, Nextcloud йәки Outlook сығарған .ics календарь файлын һайлағыҙ, йәки уның текстын индерегеҙ. Бурыстар торошона ҡарап To Do, In Progress, Done йәки Cancelled исемлегенә, ваҡиғалар Events исемлегенә башланыу һәм үтәү ваҡыттары менән күсә, шуға ла Calendar һәм Gantt күренештәрендә күренә. Категориялар һәм өҫтөнлөк билдәләргә әйләнә. Ҡабатланған элементтар бер тапҡыр индерелә.",
"import-board-instruction-googletakeout": "takeout.google.com сайтында Tasks, Keep, Mail, Calendar һәм Google Chat һайлағыҙ, экспорт булдырығыҙ һәм .zip файлын йөкләгеҙ, унан уны бында һайлағыҙ. Һәр продукт бер юлға әйләнә: Email күренеше өсөн почта, тикшереү исемлектәре менән бурыс исемлектәре һәм яҙмалар, даталары менән календарь ваҡиғалары һәм бурыстар, һәм хәбәрҙәре Chat күренеше өсөн аңлатмалар булған чат урындары. Башҡа продукттар һәм ҡушымталар индерелмәй.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-та Settings, Advanced, Export Telegram data асығыҙ, JSON форматын һайлап экспортлағыҙ, унан result.json файлын һайлағыҙ, йәки уның текстын индерегеҙ. Һәр чат Direct messages, Groups йәки Channels эсендә карточкаға әйләнә, уның хәбәрҙәре карточка аңлатмаларына әйләнә, шуға ла Chat күренеше чатты күрһәтә. Фотолар һәм файлдар индерелмәй.",
"import-board-instruction-whatsapp": "WhatsApp-та чатты асығыҙ, медиаһыҙ Export chat һайлағыҙ, һәм .txt файлын бында һайлағыҙ, йәки уның текстын индерегеҙ. Чат хәбәрҙәре ебәреүсеһе һәм ваҡыты буйынса уның аңлатмалары булған карточкаға әйләнә, шуға ла Chat күренеше уны күрһәтә. Медиа һәм система хәбәрҙәре индерелмәй.",
"import-board-instruction-discord": "Discord каналын DiscordChatExporter менән JSON форматында экспортлағыҙ һәм .json файлын һайлағыҙ, йәки уның текстын индерегеҙ. Канал үҙ категорияһында карточкаға әйләнә, уның хәбәрҙәре карточка аңлатмаларына әйләнә, шуға ла Chat күренеше каналды күрһәтә. Сервер юлға әйләнә. Ҡушымталар индерелмәй.",
"import-board-instruction-rocketchat": "Rocket.Chat-та мәғлүмәттәрегеҙҙе «My Data» бүлегендә JSON итеп экспортлағыҙ һәм ул һеҙгә ебәргән .zip файлын, йәки бер бүлмәнең экспортланған .json файлын һайлағыҙ. Һәр бүлмә карточкаға әйләнә, уның хәбәрҙәре карточка аңлатмаларына әйләнә, шуға ла Chat күренеше бүлмәне күрһәтә. WeKan Rocket.Chat-тың CSV импортлаусыһы өсөн экспортлаған .zip та уҡыла.",
"import-board-instruction-evernote": "Evernote-та яҙмаларҙы йәки яҙма дәфтәрен .enex файлы итеп экспортлағыҙ һәм уны бында һайлағыҙ, йәки уның текстын индерегеҙ. Һәр яҙма тексы, тикшереү исемлеге булараҡ бурыс билдәләре, билдәләр булараҡ тегтары һәм үтәү ваҡыты булараҡ иҫкәртеүе менән карточкаға әйләнә; иҫкәртеүе үтәлгән яҙмалар Done исемлегенә күсә. Һүрәттәр һәм ҡушылған файлдар индерелмәй.",
"tool-group-kanban": "Канбан һәм проект ҡоралдары",
"tool-group-issues": "Хаталарҙы күҙәтеү һәм версия контроле",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "У Redmine адкрыйце Issues праекта, выберыце Also available in: CSV унізе спіса, выберыце слупкі (All columns, з Description) і экспартуйце, затым устаўце CSV. Redmine называе слупкі на вашай мове, таму перад экспартам выберыце англійскую мову ў My account. Кожны стан становіцца спісам, а задачы карткамі з тыпам задачы як меткай, прызначаным карыстальнікам, аўтарам, датамі, бацькоўскай задачай і звязанымі задачамі; прыярытэт, катэгорыя, мэтавая версія, ацэнка часу, % Done і карыстальніцкія палі становяцца карыстальніцкімі палямі.",
"import-board-instruction-notion": "У Notion адкрыйце базу даных як поўную старонку, выберыце ••• і Export, затым Markdown & CSV, і выберыце спампаваны файл .zip, або CSV адной базы даных з яго, або ўстаўце гэты CSV. Слупок з назвай Status становіцца спісамі (калі яго няма, выкарыстоўваецца першы слупок, падобны да поля выбару, а справаздача аб імпарце паказвае які); радкі становяцца карткамі з назвай, меткамі, людзьмі як удзельнікамі, датамі і тэкстам старонкі як апісаннем; іншыя слупкі становяцца карыстальніцкімі палямі. Сувязі паміж запісамі, выявы і ўкладанні не імпартуюцца.",
"import-board-instruction-plane": "У Plane адкрыйце Workspace Settings, выберыце Exports, экспартуйце праекты як JSON, CSV або Excel і спампуйце файл .zip, затым выберыце гэты файл, або адзін файл з яго, або ўстаўце JSON ці CSV. Станы становяцца спісамі, праекты дарожкамі, а задачы карткамі з ідэнтыфікатарам, бацькоўскім элементам, прызначанымі карыстальнікамі, меткамі, датамі, спасылкамі і каментарыямі; прыярытэт, ацэнка, цыкл і модуль становяцца карыстальніцкімі палямі. Экспарт Plane не змяшчае апісанняў або ўкладанняў, таму яны не імпартуюцца.",
"import-board-instruction-fizzy": "У Fizzy экспартуйце ўліковы запіс у «Account settings» або свае карткі праз «Download my data» і выберыце файл .zip, які дашле вам Fizzy, або файл .json адной карткі. Дошкі становяцца дарожкамі, а слупкі — спісамі, з «Maybe?», «Not now» і «Done», як у Fizzy; карткі захоўваюць апісанне, меткі, прызначаных, крокі як кантрольны спіс, каментарыі і файлы.",
"import-board-instruction-mail": "Выберыце файл .mbox, як яго захоўваюць Thunderbird, Apple Mail, mutt або Gmail праз Google Takeout, або адно паведамленне .eml, або ўстаўце яго тэкст. Кожная размова становіцца адной карткай у спісе Inbox, з адпраўніком, атрымальнікамі і тэмай, каб яна паказвалася ў выглядзе Email; адказы становяцца яе каментарыямі. Меткі Gmail становяцца меткамі. Укладанні не імпартуюцца.",
"import-board-instruction-ical": "Выберыце файл календара .ics, як яго экспартуюць Google Calendar, Apple Calendar або Reminders, Thunderbird, Nextcloud або Outlook, або ўстаўце яго тэкст. Задачы трапляюць у To Do, In Progress, Done або Cancelled паводле свайго статусу, а падзеі ў Events, з датамі пачатку і тэрміну, каб яны паказваліся ў выглядах Calendar і Gantt. Катэгорыі і прыярытэт становяцца меткамі. Паўторныя элементы імпартуюцца адзін раз.",
"import-board-instruction-googletakeout": "На takeout.google.com выберыце Tasks, Keep, Mail, Calendar і Google Chat, стварыце экспарт і спампуйце файл .zip, потым выберыце яго тут. Кожны прадукт становіцца дарожкай: пошта для выгляду Email, спісы задач і нататкі з іх кантрольнымі спісамі, падзеі календара і задачы з датамі, і чат-прасторы, паведамленні якіх становяцца каментарыямі для выгляду Chat. Іншыя прадукты і ўкладанні не імпартуюцца.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "У Telegram Desktop адкрыйце Settings, Advanced, Export Telegram data, выберыце фармат JSON і экспартуйце, потым выберыце файл result.json, або ўстаўце яго тэкст. Кожны чат становіцца карткай у Direct messages, Groups або Channels, а яго паведамленні становяцца каментарыямі карткі, каб выгляд Chat паказваў чат. Фота і файлы не імпартуюцца.",
"import-board-instruction-whatsapp": "У WhatsApp адкрыйце чат, выберыце Export chat без медыя і выберыце тут файл .txt, або ўстаўце яго тэкст. Чат становіцца карткай, паведамленні якой з'яўляюцца яе каментарыямі ад імя адпраўніка і з часам, каб выгляд Chat паказваў яго. Медыя і сістэмныя паведамленні не імпартуюцца.",
"import-board-instruction-discord": "Экспартуйце канал Discord з дапамогай DiscordChatExporter у фармаце JSON і выберыце файл .json, або ўстаўце яго тэкст. Канал становіцца карткай у сваёй катэгорыі, а яго паведамленні становяцца каментарыямі карткі, каб выгляд Chat паказваў канал. Сервер становіцца дарожкай. Укладанні не імпартуюцца.",
"import-board-instruction-rocketchat": "У Rocket.Chat экспартуйце свае даныя ў фармаце JSON у «My Data» і выберыце файл .zip, які ён вам дашле, або экспартаваны файл .json аднаго пакоя. Кожны пакой становіцца карткай, а яго паведамленні становяцца каментарыямі карткі, каб выгляд Chat паказваў пакой. Таксама чытаецца .zip, які WeKan экспартуе для CSV-імпарцёра Rocket.Chat.",
"import-board-instruction-evernote": "У Evernote экспартуйце нататкі або нататнік як файл .enex і выберыце яго тут, або ўстаўце яго тэкст. Кожная нататка становіцца карткай з яе тэкстам, сцяжкамі задач як кантрольным спісам, тэгамі як меткамі і напамінам як тэрмінам; нататкі з выкананым напамінам трапляюць у Done. Выявы і далучаныя файлы не імпартуюцца.",
"tool-group-kanban": "Kanban і інструменты для праектаў",
"tool-group-issues": "Трэкеры праблем і кантроль версій",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "В Redmine отворете Issues на проекта, изберете Also available in: CSV в долната част на списъка, изберете колоните (All columns, включително Description) и експортирайте, след което поставете CSV. Redmine именува колоните на вашия език, затова преди експорта задайте езика на English в My account. Всяко състояние става списък, а проблемите стават карти с типа проблем като етикет, отговорника, автора, датите, родителската задача и свързаните проблеми; приоритетът, категорията, целевата версия, прогнозното време, % Done и персонализираните полета стават персонализирани полета.",
"import-board-instruction-notion": "В Notion отворете базата данни като цяла страница, изберете ••• и Export, изберете Markdown & CSV и след това изтегления .zip файл или един CSV на база данни от него, или поставете този CSV. Колона с име Status определя списъците (ако липсва, се използва първата колона, която прилича на поле за избор, и отчетът за импорта посочва коя е тя). Редовете стават карти със заглавието, етикетите, хората като членове, датите и текста на страницата като описание; останалите колони стават персонализирани полета. Релациите, изображенията и прикачените файлове не се импортират.",
"import-board-instruction-plane": "В Plane отворете Workspace Settings, изберете Exports, експортирайте проектите като JSON, CSV или Excel и изтеглете .zip файла, след което изберете този файл или един файл от него, или поставете JSON или CSV. Състоянията стават списъци, проектите стават коридори, а проблемите стават карти с идентификатора, родителския проблем, отговорниците, етикетите, датите, връзките и коментарите; приоритетът, оценката, цикълът и модулът стават персонализирани полета. Експортът на Plane не съдържа описания или прикачени файлове, затова те не се импортират.",
"import-board-instruction-fizzy": "Във Fizzy експортирайте акаунта от „Account settings“ или собствените си карти с „Download my data“ и изберете файла .zip, който Fizzy ви изпраща, или файла .json на една карта. Таблата стават коридори, а колоните стават списъци, с „Maybe?“, „Not now“ и „Done“ както във Fizzy; картите запазват описанието, етикетите, изпълнителите, стъпките като списък със задачи, коментарите и файловете си.",
"import-board-instruction-mail": "Изберете файл .mbox, както го записват Thunderbird, Apple Mail, mutt или Gmail чрез Google Takeout, или едно съобщение .eml, или поставете текста му. Всеки разговор става една карта в списъка Inbox, с подателя, получателите и темата си, така че се показва в изгледа Email; отговорите стават негови коментари. Етикетите на Gmail стават етикети. Прикачените файлове не се импортират.",
"import-board-instruction-ical": "Изберете календарен файл .ics, както го експортират Google Calendar, Apple Calendar или Reminders, Thunderbird, Nextcloud или Outlook, или поставете текста му. Задачите отиват в To Do, In Progress, Done или Cancelled според състоянието си, а събитията в Events, с началните и крайните си дати, така че се показват в изгледите Calendar и Gantt. Категориите и приоритетът стават етикети. Повтарящите се елементи се импортират веднъж.",
"import-board-instruction-googletakeout": "В takeout.google.com изберете Tasks, Keep, Mail, Calendar и Google Chat, създайте експорта и изтеглете файла .zip, след това го изберете тук. Всеки продукт става коридор: пощата за изгледа Email, списъците със задачи и бележките с техните списъци за проверка, календарните събития и задачите с дати, и чат пространствата, чиито съобщения са коментари за изгледа Chat. Другите продукти и прикачените файлове не се импортират.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "В Telegram Desktop отворете Settings, Advanced, Export Telegram data, изберете формата JSON и експортирайте, след това изберете файла result.json, или поставете текста му. Всеки чат става карта в Direct messages, Groups или Channels, а съобщенията му стават коментари на картата, така че изгледът Chat показва чата. Снимките и файловете не се импортират.",
"import-board-instruction-whatsapp": "В WhatsApp отворете чата, изберете Export chat без мултимедия и изберете тук файла .txt, или поставете текста му. Чатът става карта, чиито съобщения са нейни коментари, с подателя и часа си, така че изгледът Chat я показва. Мултимедията и системните съобщения не се импортират.",
"import-board-instruction-discord": "Експортирайте канал от Discord с DiscordChatExporter във формат JSON и изберете файла .json, или поставете текста му. Каналът става карта в своята категория, а съобщенията му стават коментари на картата, така че изгледът Chat показва канала. Сървърът става коридорът. Прикачените файлове не се импортират.",
"import-board-instruction-rocketchat": "В Rocket.Chat експортирайте данните си като JSON от „My Data“ и изберете файла .zip, който ви изпраща, или експортирания файл .json на една стая. Всяка стая става карта, а съобщенията ѝ стават коментари на картата, така че изгледът Chat показва стаята. Чете се и файлът .zip, който WeKan експортира за CSV импортиращия инструмент на Rocket.Chat.",
"import-board-instruction-evernote": "В Evernote експортирайте бележките или бележник като файл .enex и го изберете тук, или поставете текста му. Всяка бележка става карта с текста си, полетата ѝ за задачи като списък със задачи, таговете ѝ като етикети и напомнянето ѝ като краен срок; бележките с изпълнено напомняне отиват в Done. Изображенията и прикачените файлове не се импортират.",
"tool-group-kanban": "Kanban и инструменти за проекти",
"tool-group-issues": "Проследяване на проблеми и контрол на версиите",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine में, प्रोजेक्ट के Issues खोलीं, सूची के नीचे Also available in: CSV चुनीं, कॉलम चुनीं (All columns, Description के साथे) आ निर्यात करीं, फेर CSV चिपकाईं। Redmine कॉलम के नाम रउआ भाषा में रखेला, एह से निर्यात से पहिले My account में आपन भाषा अंग्रेजी करीं। हर स्टेटस एगो सूची बनेला आ इश्यू कार्ड बनेला, लेबल के रूप में ट्रैकर, जिम्मेदार, लेखक, तारीख, मूल टास्क आ संबंधित इश्यू के साथे; प्राथमिकता, श्रेणी, लक्ष्य संस्करण, अनुमानित समय, % Done आ कस्टम क्षेत्र कस्टम क्षेत्र बनेला।",
"import-board-instruction-notion": "Notion में, डेटाबेस के पूरा पन्ना के रूप में खोलीं, ••• आ Export चुनीं, Markdown & CSV चुनीं, आ जवन .zip फाइल डाउनलोड होला ओकरा के चुनीं, भा ओकरा में से एगो डेटाबेस CSV, भा ऊ CSV चिपकाईं। Status नाम वाला कॉलम सूची बनेला (ओकरा बिना, पहिला कॉलम जवन select जइसन लागेला, आ आयात रिपोर्ट बतावेला कि कवन); पंक्ति कार्ड बनेला अपना शीर्षक, लेबल के रूप में टैग, सदस्य के रूप में लोग, तारीख, आ विवरण के रूप में पन्ना के टेक्स्ट के साथे; दोसर कॉलम कस्टम क्षेत्र बनेला। संबंध, चित्र आ संलग्नक आयात ना होला।",
"import-board-instruction-plane": "Plane में, Workspace Settings खोलीं, Exports चुनीं, प्रोजेक्ट के JSON, CSV भा Excel के रूप में निर्यात करीं आ .zip फाइल डाउनलोड करीं, फेर ऊ फाइल चुनीं, भा ओकरा भीतर के एगो फाइल, भा JSON भा CSV चिपकाईं। स्टेट सूची बनेला, प्रोजेक्ट रस्ता बनेला, आ इश्यू कार्ड बनेला अपना पहचान, मूल, जिम्मेदार, लेबल, तारीख, कड़ी आ टिप्पणी के साथे; प्राथमिकता, अनुमान, साइकिल आ मॉड्यूल कस्टम क्षेत्र बनेला। Plane के निर्यात में विवरण भा संलग्नक ना होला, एह से ऊ आयात ना होला।",
"import-board-instruction-fizzy": "Fizzy में, \"Account settings\" में खाता निर्यात करीं, भा \"Download my data\" से आपन कार्ड, आ Fizzy जवन .zip फाइल भेजे ओकरा के, भा एगो कार्ड के .json फाइल चुनीं। बोर्ड रस्ता बन जाला आ कॉलम सूची बन जाला, \"Maybe?\", \"Not now\" आ \"Done\" Fizzy नियर रहेला; कार्ड आपन विवरण, लेबल, जिम्मेदार लोग, कदम जाँच सूची के रूप में, टिप्पणी आ फाइल रखेला।",
"import-board-instruction-mail": "एगो .mbox फाइल चुनीं, जइसे Thunderbird, Apple Mail, mutt भा Google Takeout के जरिए Gmail ओकरा सहेजेला, भा एगो अकेल .eml संदेश, भा ओकर लिखाई चिपकाईं। हर बातचीत आपन भेजे वाला, पावे वाला आ विषय के साथे Inbox सूची में एगो कार्ड बन जाला, ताकि ऊ Email दृश्य में देखाई दे; जवाब ओकर टिप्पणी बन जाला। Gmail के लेबल लेबल बन जाला। संलग्नक आयात ना होला।",
"import-board-instruction-ical": "एगो .ics कैलेंडर फाइल चुनीं, जइसे Google Calendar, Apple Calendar भा Reminders, Thunderbird, Nextcloud भा Outlook ओकरा निर्यात करेला, भा ओकर लिखाई चिपकाईं। काम आपन स्थिति के हिसाब से To Do, In Progress, Done भा Cancelled में जाला, आ घटना Events में, आपन शुरू आ नियत तारीख के साथे, ताकि ऊ Calendar आ Gantt दृश्य में देखाई दे। श्रेणी आ प्राथमिकता लेबल बन जाला। दोहरावे वाला चीज एक बेर आयात होला।",
"import-board-instruction-googletakeout": "takeout.google.com पर Tasks, Keep, Mail, Calendar आ Google Chat चुनीं, निर्यात बनाईं आ .zip फाइल डाउनलोड करीं, फेर ओकरा इहाँ चुनीं। हर उत्पाद एगो रस्ता बन जाला: Email दृश्य खातिर मेल, जाँच सूची के साथे काम के सूची आ नोट, तारीख के साथे कैलेंडर घटना आ काम, आ चैट जगह जेकर संदेश Chat दृश्य खातिर टिप्पणी होला। दोसर उत्पाद आ संलग्नक आयात ना होला।",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop में Settings, Advanced, Export Telegram data खोलीं, JSON फॉर्मेट चुन के निर्यात करीं, फेर result.json फाइल चुनीं, भा ओकर लिखाई चिपकाईं। हर चैट Direct messages, Groups भा Channels में एगो कार्ड बन जाला, आ ओकर संदेश कार्ड के टिप्पणी बन जाला, ताकि Chat दृश्य चैट देखावे। फोटो आ फाइल आयात ना होला।",
"import-board-instruction-whatsapp": "WhatsApp में चैट खोलीं, बिना मीडिया के Export chat चुनीं, आ .txt फाइल इहाँ चुनीं, भा ओकर लिखाई चिपकाईं। चैट एगो कार्ड बन जाला जेकर संदेश, भेजे वाला आ समय के हिसाब से, ओकर टिप्पणी होला, ताकि Chat दृश्य ओकरा देखावे। मीडिया आ सिस्टम संदेश आयात ना होला।",
"import-board-instruction-discord": "DiscordChatExporter से JSON फॉर्मेट में एगो Discord चैनल निर्यात करीं आ .json फाइल चुनीं, भा ओकर लिखाई चिपकाईं। चैनल आपन श्रेणी में एगो कार्ड बन जाला, आ ओकर संदेश कार्ड के टिप्पणी बन जाला, ताकि Chat दृश्य चैनल देखावे। सर्वर रस्ता बन जाला। संलग्नक आयात ना होला।",
"import-board-instruction-rocketchat": "Rocket.Chat में, \"My Data\" में आपन डेटा JSON के रूप में निर्यात करीं आ ऊ जवन .zip फाइल भेजे ओकरा के, भा एगो रूम के निर्यात कइल .json फाइल चुनीं। हर रूम एगो कार्ड बन जाला आ ओकर संदेश कार्ड के टिप्पणी बन जाला, ताकि Chat दृश्य रूम देखावे। WeKan जवन .zip Rocket.Chat के CSV आयातक खातिर निर्यात करेला, ऊहो पढ़ल जाला।",
"import-board-instruction-evernote": "Evernote में नोट भा एगो नोटबुक के .enex फाइल के रूप में निर्यात करीं आ ओकरा इहाँ चुनीं, भा ओकर लिखाई चिपकाईं। हर नोट आपन लिखाई, जाँच सूची के रूप में आपन काम के बक्सा, लेबल के रूप में आपन टैग आ नियत तारीख के रूप में आपन याद दिलावे वाला के साथे एगो कार्ड बन जाला; जवना नोट के याद दिलावे वाला पूरा हो गइल बा ऊ Done में जाला। फोटो आ जुड़ल फाइल आयात ना होला।",
"tool-group-kanban": "कानबान आ परियोजना औजार",
"tool-group-issues": "समस्या ट्रैकर आ संस्करण नियंत्रण",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Long Redmine, openem Issues blong projek, jusum Also available in: CSV long botom blong lis, jusum ol kolum (All columns, wetem Description) mo sendem i go, afta pestem CSV. Redmine i putum nem blong ol kolum long lanwis blong yu, ale jenisim lanwis blong yu i go long Inglis long My account bifo yu sendem i go. Evri stetas i kam wan lis mo ol isiu oli kam ol kad, wetem treka olsem mak, man we i gat wok, man we i raetem, deit, papa wok mo ol isiu we oli joen; praeoriti, kategori, vesen we oli wantem kasem, taem we oli tingbaot, % Done mo ol fil blong yu oli kam ol fil blong yu.",
"import-board-instruction-notion": "Long Notion, openem database olsem wan fulwan pej, jusum ••• mo Export, jusum Markdown & CSV, mo jusum fael .zip we i daonlod, o wan database CSV long hem, o pestem CSV ia. Wan kolum we nem blong hem Status i kam ol lis (sapos i no gat, fes kolum we i luk olsem wan jus i mekem, mo ripot blong import i talem wanem); ol laen oli kam ol kad wetem nem, tag olsem mak, ol man olsem memba, deit, mo teks blong pej olsem stori; ol narafala kolum oli kam ol fil blong yu. Ol rilesen, pija mo atajmen oli no kam.",
"import-board-instruction-plane": "Long Plane, openem Workspace Settings, jusum Exports, sendem ol projek i go olsem JSON, CSV o Excel mo daonlodem fael .zip, afta jusum fael ia, o wan fael insaed long hem, o pestem JSON o CSV. Ol stet oli kam ol lis, ol projek oli kam ol rod, mo ol isiu oli kam ol kad wetem namba, papa, man we i gat wok, mak, deit, link mo toktok blong olgeta; praeoriti, estimet, saekol mo modiul oli kam ol fil blong yu. Eksport blong Plane i no gat stori o atajmen, ale oli no kam.",
"import-board-instruction-fizzy": "Long Fizzy, eksportem akaon long \"Account settings\", o ol kad blong yu nomo wetem \"Download my data\", mo jusum .zip fael we Fizzy i sanem long yu, o .json fael blong wan kad. Ol bod oli kam ol rod mo ol kolom oli kam ol lis, wetem \"Maybe?\", \"Not now\" mo \"Done\" olsem long Fizzy; ol kad oli kipim stori, ol mak, ol man we i gat wok, ol step olsem jeklis, ol toktok mo ol fael blong olgeta.",
"import-board-instruction-mail": "Jusum wan .mbox fael, olsem Thunderbird, Apple Mail, mutt o Gmail tru long Google Takeout i sevem, o wan .eml mesej nomo, o pastem teks blong hem. Evri storian i kam wan kad long lis Inbox, wetem man we i sendem, ol man we i kasem mo nem blong hem, blong i soem long luk Email; ol ansa i kam ol toktok blong hem. Ol mak blong Gmail i kam ol mak. Ol fael we i joen i no kam insaed.",
"import-board-instruction-ical": "Jusum wan .ics kalenda fael, olsem Google Calendar, Apple Calendar o Reminders, Thunderbird, Nextcloud o Outlook i eksportem, o pastem teks blong hem. Ol wok i go long To Do, In Progress, Done o Cancelled folem stejes blong olgeta, mo ol samting we i hapen i go long Events, wetem dei blong stat mo dei blong finis, blong oli soem long luk Calendar mo Gantt. Ol kaen mo praeoriti i kam ol mak. Ol samting we i kambak oltaem oli kam insaed wan taem nomo.",
"import-board-instruction-googletakeout": "Long takeout.google.com, jusum Tasks, Keep, Mail, Calendar mo Google Chat, mekem eksport mo daonlodem .zip fael, afta jusum hem long ples ia. Evri prodak i kam wan rod: meel blong luk Email, ol lis blong wok mo ol not wetem ol jeklis blong olgeta, ol samting blong kalenda mo ol wok wetem dei, mo ol ples blong jat we ol mesej blong olgeta oli toktok blong luk Chat. Ol narafala prodak mo ol fael we i joen i no kam insaed.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Long Telegram Desktop, openem Settings, Advanced, Export Telegram data, jusum JSON fomat mo eksport, afta jusum result.json fael, o pastem teks blong hem. Evri jat i kam wan kad long Direct messages, Groups o Channels, mo ol mesej blong hem oli kam ol toktok blong kad, blong luk Chat i soem jat. Ol foto mo fael oli no kam insaed.",
"import-board-instruction-whatsapp": "Long WhatsApp, openem jat, jusum Export chat we i no gat media, mo jusum .txt fael long ples ia, o pastem teks blong hem. Jat i kam wan kad we ol mesej blong hem oli ol toktok blong hem, folem man we i sendem mo taem, blong luk Chat i soem. Media mo ol mesej blong sistem oli no kam insaed.",
"import-board-instruction-discord": "Eksportem wan Discord jenel wetem DiscordChatExporter long JSON fomat mo jusum .json fael, o pastem teks blong hem. Jenel i kam wan kad long kaen blong hem, mo ol mesej blong hem oli kam ol toktok blong kad, blong luk Chat i soem jenel. Seva i kam rod. Ol fael we i joen i no kam insaed.",
"import-board-instruction-rocketchat": "Long Rocket.Chat, eksportem data blong yu olsem JSON long \"My Data\" mo jusum .zip fael we i sanem long yu, o .json fael we oli eksportem blong wan rum. Evri rum i kam wan kad mo ol mesej blong hem oli kam ol toktok blong kad, blong luk Chat i soem rum. Oli ridim tu .zip we WeKan i eksportem blong CSV importa blong Rocket.Chat.",
"import-board-instruction-evernote": "Long Evernote, eksportem ol not o wan buk blong not olsem wan .enex fael mo jusum hem long ples ia, o pastem teks blong hem. Evri not i kam wan kad wetem teks blong hem, ol bokis blong wok olsem wan jeklis, ol tag blong hem olsem ol mak mo rimaenda blong hem olsem dei blong finis; ol not we rimaenda blong olgeta i finis oli go long Done. Ol pija mo ol fael we i joen i no kam insaed.",
"tool-group-kanban": "Ol tul blong Kanban mo projek",
"tool-group-issues": "Ol tul blong folem problem mo kontrol blong ol vesen",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine kɔnɔ, porozɛ ka Issues da wuli, Also available in: CSV sugandi lisiti duguma, kolɔnw sugandi (All columns, ni Description ye) ka a labɔ, o kɔ CSV don. Redmine bɛ kolɔnw tɔgɔ da i ka kan na, o la i ka kan sigi angilɛkan na My account kɔnɔ sani i ka a labɔ. Cogoya kelen-kelen bɛɛ bɛ kɛ lisiti ye ani gɛlɛyaw bɛ kɛ kartiw ye, ni tracker ye i n'a fɔ taamasiyɛn, baarakɛla, sɛbɛnbaga, donw, baara faden ani gɛlɛya sirilenw; ɲɛfɛrɔ, suguya, version laɲinilen, waati jatelen, % Done ani foro kɛrɛnkɛrɛnnenw bɛ kɛ foro kɛrɛnkɛrɛnnenw ye.",
"import-board-instruction-notion": "Notion kɔnɔ, kunnafonimarayɔrɔ da wuli i n'a fɔ ɲɛ dafalen, ••• ni Export sugandi, Markdown & CSV sugandi, ani .zip fisiye min jiginna, o sugandi, walima kunnafonimarayɔrɔ CSV kelen min bɛ a kɔnɔ, walima o CSV don. Kolɔn min tɔgɔ ye Status, o bɛ kɛ lisitiw ye (ni o tɛ yen, kolɔn fɔlɔ min bɛ i n'a fɔ sugandili, o bɛ kɛ, ani donni rapɔɔri b'a fɔ min don); sirandaw bɛ kɛ kartiw ye ni u tɔgɔ, taamasiyɛnw i n'a fɔ labelw, mɔgɔw i n'a fɔ tɔndenw, donw, ani ɲɛ sɛbɛnni i n'a fɔ ɲɛfɔli; kolɔn wɛrɛw bɛ kɛ foro kɛrɛnkɛrɛnnenw ye. Jɛɲɔgɔnyaw, jaw ani nɔrɔlenw tɛ don.",
"import-board-instruction-plane": "Plane kɔnɔ, Workspace Settings da wuli, Exports sugandi, porozɛw labɔ i n'a fɔ JSON, CSV walima Excel ka .zip fisiye jigin, o kɔ o fisiye sugandi, walima fisiye kelen min bɛ a kɔnɔ, walima JSON walima CSV don. Cogoyaw bɛ kɛ lisitiw ye, porozɛw bɛ kɛ siraw ye, ani gɛlɛyaw bɛ kɛ kartiw ye ni u ka dɔnnikɛtaamasiyɛn, faden, baarakɛlaw, taamasiyɛnw, donw, sirajɛw ani hakilinaw ye; ɲɛfɛrɔ, jateminɛ, tasuma ani module bɛ kɛ foro kɛrɛnkɛrɛnnenw ye. Plane ka labɔli tɛ ni ɲɛfɔliw walima nɔrɔlenw ye, o la u tɛ don.",
"import-board-instruction-fizzy": "Fizzy kɔnɔ, jatebila bɔ \"Account settings\" la, walima i yɛrɛ ka kartiw ni \"Download my data\" ye, ka .zip dosiye min Fizzy b'a ci i ma o sugandi, walima karti kelen ka .json dosiye. Walanw bɛ kɛ siraw ye ani kolɔnw bɛ kɛ sɛbɛnw ye, \"Maybe?\", \"Not now\" ani \"Done\" bɛ to i n'a fɔ Fizzy kɔnɔ; kartiw b'u ka ɲɛfɔli, taamasiyɛnw, baarakɛlaw, taabolow i n'a fɔ sɛgɛsɛgɛli sɛbɛn, hakilinaw ani dosiyew mara.",
"import-board-instruction-mail": ".mbox dosiye dɔ sugandi, i n'a fɔ Thunderbird, Apple Mail, mutt walima Gmail b'a mara cogo min na Google Takeout fɛ, walima .eml cikan kelen, walima a sɛbɛnni bila yan. Baro kelen-kelen bɛɛ bɛ kɛ karti kelen ye Inbox sɛbɛn kɔnɔ, a cibaa, a sɔrɔbagaw ani a kunkan, walasa a ka ye Email yecogo la; jaabiw bɛ kɛ a hakilinaw ye. Gmail taamasiyɛnw bɛ kɛ taamasiyɛnw ye. Fɛn farali tɛ don.",
"import-board-instruction-ical": ".ics kalandiriye dosiye dɔ sugandi, i n'a fɔ Google Calendar, Apple Calendar walima Reminders, Thunderbird, Nextcloud walima Outlook b'a bɔ cogo min na, walima a sɛbɛnni bila yan. Baaraw bɛ taa To Do, In Progress, Done walima Cancelled la u cogoya kan, ani ko kɛlenw bɛ taa Events la, u daminɛ don ani u laban waati, walasa u ka ye Calendar ani Gantt yecogow la. Suguyaw ani kɔrɔtalenya bɛ kɛ taamasiyɛnw ye. Fɛn segintaw bɛ don siɲɛ kelen.",
"import-board-instruction-googletakeout": "takeout.google.com kan, Tasks, Keep, Mail, Calendar ani Google Chat sugandi, bɔli dilan ka .zip dosiye jigin, o kɔ k'a sugandi yan. Fɛn kelen-kelen bɛɛ bɛ kɛ sira ye: bataki Email yecogo kama, baara sɛbɛnw ani hakilijigin sɛbɛnw u sɛgɛsɛgɛli sɛbɛnw fɛ, kalandiriye ko kɛlenw ani baaraw u donw fɛ, ani baro yɔrɔw minnu cikanw ye hakilinaw ye Chat yecogo kama. Fɛn tɔw ani fɛn farali tɛ don.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop kɔnɔ, Settings, Advanced, Export Telegram data da wuli, JSON cogoya sugandi ka bɔli kɛ, o kɔ ka result.json dosiye sugandi, walima a sɛbɛnni bila yan. Baro kelen-kelen bɛɛ bɛ kɛ karti ye Direct messages, Groups walima Channels kɔnɔ, ani a cikanw bɛ kɛ karti hakilinaw ye, walasa Chat yecogo ka baro jira. Jaw ani dosiyew tɛ don.",
"import-board-instruction-whatsapp": "WhatsApp kɔnɔ, baro da wuli, Export chat sugandi media tɛ min na, ka .txt dosiye sugandi yan, walima a sɛbɛnni bila yan. Baro bɛ kɛ karti ye min cikanw ye a hakilinaw ye, u cibaa ani u waati la, walasa Chat yecogo k'a jira. Media ani sisitɛmu cikanw tɛ don.",
"import-board-instruction-discord": "Discord kanali dɔ bɔ ni DiscordChatExporter ye JSON cogoya la ka .json dosiye sugandi, walima a sɛbɛnni bila yan. Kanali bɛ kɛ karti ye a suguya kɔnɔ, ani a cikanw bɛ kɛ karti hakilinaw ye, walasa Chat yecogo ka kanali jira. Sɛriwɛri bɛ kɛ sira ye. Fɛn farali tɛ don.",
"import-board-instruction-rocketchat": "Rocket.Chat kɔnɔ, i ka kunnafoniw bɔ JSON cogoya la \"My Data\" kɔnɔ ka .zip dosiye min b'a ci i ma o sugandi, walima so kelen ka .json dosiye bɔlen. So kelen-kelen bɛɛ bɛ kɛ karti ye ani a cikanw bɛ kɛ karti hakilinaw ye, walasa Chat yecogo ka so jira. .zip min WeKan b'a bɔ Rocket.Chat ka CSV donnan kama, o fana bɛ kalan.",
"import-board-instruction-evernote": "Evernote kɔnɔ, hakilijigin sɛbɛnw walima sɛbɛnbon dɔ bɔ .enex dosiye ye ka a sugandi yan, walima a sɛbɛnni bila yan. Hakilijigin sɛbɛn kelen-kelen bɛɛ bɛ kɛ karti ye ni a sɛbɛnni ye, a baara kɛsuw sɛgɛsɛgɛli sɛbɛn ye, a tagw taamasiyɛnw ye ani a hakilijigin laban waati ye; hakilijigin sɛbɛn minnu hakilijigin bannen don, olu bɛ taa Done la. Jaw ani dosiye farali tɛ don.",
"tool-group-kanban": "Kanban ani porozɛ minɛnw",
"tool-group-issues": "Gɛlɛyaw nɔfɛtaama ani bɔli sugandili kɔlɔsili",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-এ প্রকল্পের Issues খুলে তালিকার নিচে Also available in: CSV বেছে নিন। কলাম বেছে (All columns, Description-সহ) রপ্তানি করে CSV পেস্ট করুন। Redmine আপনার ভাষায় কলামের নাম দেয়, তাই রপ্তানির আগে My account-এ ভাষা English করুন। প্রতিটি অবস্থা তালিকা এবং ইস্যুগুলো কার্ড হয়; ট্র্যাকার লেবেল হয় এবং দায়িত্বপ্রাপ্ত, লেখক, তারিখ, মূল কাজ ও সম্পর্কিত ইস্যু বজায় থাকে। অগ্রাধিকার, বিভাগ, লক্ষ্য সংস্করণ, আনুমানিক সময়, % Done ও কাস্টম ক্ষেত্রগুলো কাস্টম ক্ষেত্র হয়।",
"import-board-instruction-notion": "Notion-এ ডেটাবেসটি পুরো পৃষ্ঠা হিসেবে খুলে ••• ও Export বেছে Markdown & CSV নির্বাচন করুন। নামানো .zip ফাইল অথবা তার ভেতরের একটি ডেটাবেস CSV বেছে নিন, বা CSV পেস্ট করুন। Status নামের কলাম থেকে তালিকা হয় (না থাকলে নির্বাচনী তালিকার মতো প্রথম কলামটি ব্যবহৃত হয় এবং আমদানি প্রতিবেদনে সেটি জানানো হয়)। সারিগুলো কার্ড হয়; শিরোনাম, ট্যাগ লেবেল হিসেবে, ব্যক্তি সদস্য হিসেবে, তারিখ এবং পৃষ্ঠার লেখা বিবরণ হিসেবে থাকে। অন্য কলামগুলো কাস্টম ক্ষেত্র হয়। সম্পর্ক, ছবি ও সংযুক্তি আমদানি হয় না।",
"import-board-instruction-plane": "Plane-এ Workspace Settings খুলে Exports বেছে প্রকল্পগুলো JSON, CSV বা Excel হিসেবে রপ্তানি করে .zip ফাইল নামান। তারপর ওই ফাইল অথবা তার ভেতরের একটি ফাইল বেছে নিন, বা JSON বা CSV পেস্ট করুন। অবস্থাগুলো তালিকা, প্রকল্পগুলো সাঁতারপথ এবং ইস্যুগুলো কার্ড হয়; শনাক্তকারী, মূল ইস্যু, দায়িত্বপ্রাপ্ত, লেবেল, তারিখ, লিংক ও মন্তব্য বজায় থাকে। অগ্রাধিকার, আনুমানিক পরিমাণ, চক্র ও মডিউল কাস্টম ক্ষেত্র হয়। Plane-এর রপ্তানিতে বিবরণ বা সংযুক্তি নেই, তাই সেগুলো আমদানি হয় না।",
"import-board-instruction-fizzy": "Fizzy-তে, \"Account settings\"-এ অ্যাকাউন্টটি রপ্তানি করুন, অথবা \"Download my data\" দিয়ে আপনার নিজের কার্ডগুলো, এবং Fizzy আপনাকে যে .zip ফাইল পাঠায় সেটি, অথবা একটি কার্ডের .json ফাইল বেছে নিন। বোর্ডগুলো সাঁতারপথ হয় এবং কলামগুলো তালিকা হয়, \"Maybe?\", \"Not now\" ও \"Done\" Fizzy-র মতোই থাকে; কার্ডগুলো তাদের বিবরণ, লেবেল, দায়িত্বপ্রাপ্ত ব্যক্তি, চেকলিস্ট হিসেবে ধাপ, মন্তব্য ও ফাইল রাখে।",
"import-board-instruction-mail": "একটি .mbox ফাইল বেছে নিন, যেমন Thunderbird, Apple Mail, mutt বা Google Takeout-এর মাধ্যমে Gmail সংরক্ষণ করে, অথবা একটি একক .eml বার্তা, অথবা এর লেখা পেস্ট করুন। প্রতিটি কথোপকথন তার প্রেরক, প্রাপক ও বিষয় সহ Inbox তালিকায় একটি কার্ড হয়, যাতে এটি Email দৃশ্যে দেখা যায়; উত্তরগুলো এর মন্তব্য হয়। Gmail লেবেলগুলো লেবেল হয়। সংযুক্তি আমদানি করা হয় না।",
"import-board-instruction-ical": "একটি .ics পঞ্জিকা ফাইল বেছে নিন, যেমন Google Calendar, Apple Calendar বা Reminders, Thunderbird, Nextcloud বা Outlook রপ্তানি করে, অথবা এর লেখা পেস্ট করুন। কাজগুলো তাদের অবস্থা অনুযায়ী To Do, In Progress, Done বা Cancelled-এ যায়, এবং ইভেন্টগুলো Events-এ, তাদের শুরু ও নির্ধারিত তারিখ সহ, যাতে সেগুলো Calendar ও Gantt দৃশ্যে দেখা যায়। বিভাগ ও অগ্রাধিকার লেবেল হয়। পুনরাবৃত্ত আইটেম একবার আমদানি করা হয়।",
"import-board-instruction-googletakeout": "takeout.google.com-এ Tasks, Keep, Mail, Calendar ও Google Chat বেছে নিন, রপ্তানি তৈরি করুন এবং .zip ফাইলটি ডাউনলোড করুন, তারপর এখানে এটি বেছে নিন। প্রতিটি পণ্য একটি সাঁতারপথ হয়: Email দৃশ্যের জন্য মেইল, চেকলিস্ট সহ কাজের তালিকা ও নোট, তারিখ সহ পঞ্জিকার ইভেন্ট ও কাজ, এবং চ্যাট স্পেস যার বার্তাগুলো Chat দৃশ্যের জন্য মন্তব্য। অন্যান্য পণ্য ও সংযুক্তি আমদানি করা হয় না।",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-এ Settings, Advanced, Export Telegram data খুলুন, JSON ফরম্যাট বেছে নিয়ে রপ্তানি করুন, তারপর result.json ফাইলটি বেছে নিন, অথবা এর লেখা পেস্ট করুন। প্রতিটি চ্যাট Direct messages, Groups বা Channels-এ একটি কার্ড হয়, এবং এর বার্তাগুলো কার্ডের মন্তব্য হয়, যাতে Chat দৃশ্য চ্যাটটি দেখায়। ছবি ও ফাইল আমদানি করা হয় না।",
"import-board-instruction-whatsapp": "WhatsApp-এ চ্যাটটি খুলুন, মিডিয়া ছাড়া Export chat বেছে নিন, এবং এখানে .txt ফাইলটি বেছে নিন, অথবা এর লেখা পেস্ট করুন। চ্যাটটি একটি কার্ড হয় যার বার্তাগুলো, প্রেরক ও সময় অনুযায়ী, এর মন্তব্য, যাতে Chat দৃশ্য এটি দেখায়। মিডিয়া ও সিস্টেম বার্তা আমদানি করা হয় না।",
"import-board-instruction-discord": "DiscordChatExporter দিয়ে JSON ফরম্যাটে একটি Discord চ্যানেল রপ্তানি করুন এবং .json ফাইলটি বেছে নিন, অথবা এর লেখা পেস্ট করুন। চ্যানেলটি তার বিভাগে একটি কার্ড হয়, এবং এর বার্তাগুলো কার্ডের মন্তব্য হয়, যাতে Chat দৃশ্য চ্যানেলটি দেখায়। সার্ভারটি সাঁতারপথ হয়। সংযুক্তি আমদানি করা হয় না।",
"import-board-instruction-rocketchat": "Rocket.Chat-এ, \"My Data\"-তে আপনার ডেটা JSON হিসেবে রপ্তানি করুন এবং এটি আপনাকে যে .zip ফাইল পাঠায় সেটি, অথবা একটি রুমের রপ্তানি করা .json ফাইল বেছে নিন। প্রতিটি রুম একটি কার্ড হয় এবং এর বার্তাগুলো কার্ডের মন্তব্য হয়, যাতে Chat দৃশ্য রুমটি দেখায়। Rocket.Chat-এর CSV আমদানিকারকের জন্য WeKan যে .zip রপ্তানি করে সেটিও পড়া হয়।",
"import-board-instruction-evernote": "Evernote-এ নোটগুলো বা একটি নোটবুক .enex ফাইল হিসেবে রপ্তানি করুন এবং এখানে এটি বেছে নিন, অথবা এর লেখা পেস্ট করুন। প্রতিটি নোট তার লেখা, চেকলিস্ট হিসেবে তার করণীয় বাক্স, লেবেল হিসেবে তার ট্যাগ এবং নির্ধারিত তারিখ হিসেবে তার অনুস্মারক সহ একটি কার্ড হয়; যেসব নোটের অনুস্মারক সম্পন্ন সেগুলো Done-এ যায়। ছবি ও সংযুক্ত ফাইল আমদানি করা হয় না।",
"tool-group-kanban": "কানবান ও প্রকল্প টুল",
"tool-group-issues": "সমস্যা ট্র্যাকার ও সংস্করণ নিয়ন্ত্রণ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine ནང་ལས་འཆར་གྱི་ Issues ཁ་ཕྱེ་ནས་ཐོ་གཞུང་གི་འོག་གི་ Also available in: CSV འདེམས་ཏེ་ཀ་གདན་འདེམས། (All columns, with Description) ཕྱིར་འདྲེན་བྱས་རྗེས་ CSV སྦྱོར་རོགས། Redmine གྱིས་ཀ་གདན་རྣམས་ཁྱེད་ཀྱི་སྐད་ཡིག་ཐོག་མིང་འདོགས་པས་ཕྱིར་འདྲེན་མ་བྱས་གོང་ My account ནང་སྐད་ཡིག་དབྱིན་ཡིག་ཏུ་སྒྲིག་རོགས། གནས་སྟངས་རེ་རེ་ཐོ་གཞུང་དང་གནད་དོན་རྣམས་བྱང་བུར་འགྱུར་ཞིང་། tracker རྟགས་ལྟར། འགན་འཁུར་བ། རྩོམ་པ་པོ། ཚེས་གྲངས། ཕ་མའི་ལས་འགན་དང་འབྲེལ་ཡོད་གནད་དོན་བཅས་ཡོད། གལ་གནད་རིམ་པ། སྡེ་ཚན། དམིགས་ཡུལ་པར་གཞི། ཚོད་དཔག་དུས་ཚོད། % Done དང་རང་བཟོས་ས་ཁོངས་རྣམས་རང་བཟོས་ས་ཁོངས་སུ་འགྱུར།",
"import-board-instruction-notion": "Notion ནང་གཞི་གྲངས་མཛོད་ཤོག་ངོས་ཧྲིལ་པོར་ཁ་ཕྱེ་ནས་ ••• དང་ Export འདེམས། Markdown & CSV འདེམས་ཏེ་ཕབ་ལེན་བྱས་པའི་ .zip ཡིག་ཆའམ། དེའི་ནང་གི་གཞི་གྲངས་མཛོད་ CSV གཅིག་འདེམས་པའམ། CSV དེ་སྦྱོར་རོགས། Status ཞེས་པའི་ཀ་གདན་ཐོ་གཞུང་དུ་འགྱུར། (དེ་མེད་ན་ select འདྲ་བའི་ཀ་གདན་དང་པོ་དེ་འགྱུར་ཞིང་ནང་འདྲེན་སྙན་ཐོར་གང་ཡིན་གསལ།) ཕྲེང་རྣམས་བྱང་བུར་འགྱུར་ཞིང་། མིང་། རྟགས་ཁ་བྱང་ལྟར། མི་ཚོགས་མི་ལྟར། ཚེས་གྲངས་དང་ཤོག་ངོས་ཀྱི་ཡི་གེ་འགྲེལ་བཤད་ལྟར་ཡོད། ཀ་གདན་གཞན་རྣམས་རང་བཟོས་ས་ཁོངས་སུ་འགྱུར། འབྲེལ་བ། པར་རིས་དང་ཟུར་སྦྱར་ནང་འདྲེན་མི་བྱེད།",
"import-board-instruction-plane": "Plane ནང་ Workspace Settings ཁ་ཕྱེ་ནས་ Exports འདེམས། ལས་འཆར་རྣམས་ JSON, CSV ཡང་ན་ Excel ལྟར་ཕྱིར་འདྲེན་བྱས་ཏེ་ .zip ཡིག་ཆ་ཕབ་ལེན་བྱས་རྗེས་ཡིག་ཆ་དེ་འདེམས་པའམ། དེའི་ནང་གི་ཡིག་ཆ་གཅིག་འདེམས་པའམ། JSON ཡང་ན་ CSV སྦྱོར་རོགས། གནས་སྟངས་རྣམས་ཐོ་གཞུང་། ལས་འཆར་རྣམས་ཆུ་ལམ། གནད་དོན་རྣམས་བྱང་བུར་འགྱུར་ཞིང་། ངོས་འཛིན་རྟགས། ཕ་མ། འགན་འཁུར་བ། རྟགས། ཚེས་གྲངས། དྲ་མཐུད་དང་མཆན་བུ་བཅས་ཡོད། གལ་གནད་རིམ་པ། ཚོད་དཔག cycle དང་ module རང་བཟོས་ས་ཁོངས་སུ་འགྱུར། Plane ཡི་ཕྱིར་འདྲེན་ནང་འགྲེལ་བཤད་དང་ཟུར་སྦྱར་མེད་པས་ནང་འདྲེན་མི་བྱེད།",
"import-board-instruction-fizzy": "Fizzy ནང་ \"Account settings\" ནས་རྩིས་ཐོ་ཕྱིར་འདྲེན་བྱེད། ཡང་ན་ \"Download my data\" ཡིས་རང་གི་ཤོག་བྱང་རྣམས་ཕྱིར་འདྲེན་བྱས་ནས་ Fizzy ཡིས་ཁྱེད་ལ་བསྐུར་བའི་ .zip ཡིག་ཆ་འམ་ཤོག་བྱང་གཅིག་གི་ .json ཡིག་ཆ་འདེམས། བྱང་བུ་རྣམས་ལམ་དུ་འགྱུར། སྟར་ཕྲེང་རྣམས་ཐོ་གཞུང་དུ་འགྱུར། \"Maybe?\" དང་ \"Not now\" དང་ \"Done\" རྣམས་ Fizzy ནང་བཞིན་ཡིན། ཤོག་བྱང་རྣམས་ཀྱིས་རང་གི་འགྲེལ་བཤད་དང་ཁ་བྱང་། འགན་འཁུར་བ། ཞིབ་བཤེར་ཐོ་གཞུང་དུ་གོམ་རིམ། བསམ་ཚུལ། ཡིག་ཆ་རྣམས་ཉར།",
"import-board-instruction-mail": "Thunderbird དང་ Apple Mail། mutt ཡང་ན་ Google Takeout བརྒྱུད་ Gmail གྱིས་ཉར་བ་ལྟར་གྱི་ .mbox ཡིག་ཆ་གཅིག་གམ། .eml འཕྲིན་ཡིག་གཅིག་འདེམས། ཡང་ན་དེའི་ཡི་གེ་སྦྱར། ཁ་བརྡ་རེ་རེ་ནི་གཏོང་མཁན་དང་། ལེན་མཁན། བརྗོད་གཞི་བཅས་ Inbox ཐོ་གཞུང་ནང་ཤོག་བྱང་གཅིག་ཏུ་འགྱུར་བས་ Email མཐོང་སྣང་ནང་མངོན། ལན་རྣམས་དེའི་བསམ་ཚུལ་དུ་འགྱུར། Gmail གྱི་ཁ་བྱང་རྣམས་ཁ་བྱང་དུ་འགྱུར། ཟུར་སྦྱར་ནང་འདྲེན་མི་བྱེད།",
"import-board-instruction-ical": "Google Calendar དང་ Apple Calendar ཡང་ན་ Reminders། Thunderbird། Nextcloud ཡང་ན་ Outlook གྱིས་ཕྱིར་འདྲེན་བྱས་པ་ལྟར་གྱི་ .ics ལོ་ཐོའི་ཡིག་ཆ་གཅིག་འདེམས། ཡང་ན་དེའི་ཡི་གེ་སྦྱར། ལས་འགན་རྣམས་དེའི་གནས་སྟངས་ལྟར་ To Do དང་ In Progress། Done ཡང་ན་ Cancelled ལ་འགྲོ། བྱུང་རིམ་རྣམས་ Events ལ་འགྲོ། འགོ་འཛུགས་དང་དུས་ཚོད་ཚང་བའི་ཚེས་གྲངས་བཅས་ཡིན་པས་ Calendar དང་ Gantt མཐོང་སྣང་ནང་མངོན། རིགས་དང་གལ་ཆེའི་རིམ་པ་ཁ་བྱང་དུ་འགྱུར། བསྐྱར་ཟློས་རྣམ་གྲངས་ཐེངས་གཅིག་ལ་ནང་འདྲེན་བྱེད།",
"import-board-instruction-googletakeout": "takeout.google.com ནང་ Tasks དང་ Keep། Mail། Calendar། Google Chat འདེམས། ཕྱིར་འདྲེན་བཟོས་ནས་ .zip ཡིག་ཆ་ཕབ་ལེན་བྱེད། དེ་ནས་འདིར་འདེམས། ཐོན་རྫས་རེ་རེ་ལམ་གཅིག་ཏུ་འགྱུར། Email མཐོང་སྣང་ཆེད་དུ་གློག་འཕྲིན། ཞིབ་བཤེར་ཐོ་གཞུང་བཅས་པའི་ལས་འགན་ཐོ་གཞུང་དང་ཟིན་བྲིས། ཚེས་གྲངས་བཅས་པའི་ལོ་ཐོའི་བྱུང་རིམ་དང་ལས་འགན། འཕྲིན་ཡིག་རྣམས་ Chat མཐོང་སྣང་གི་བསམ་ཚུལ་ཡིན་པའི་ཁ་བརྡའི་ས་སྟོང་། ཐོན་རྫས་གཞན་དང་ཟུར་སྦྱར་ནང་འདྲེན་མི་བྱེད།",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop ནང་ Settings, Advanced, Export Telegram data ཁ་ཕྱེ། JSON རྣམ་གཞག་འདེམས་ནས་ཕྱིར་འདྲེན་བྱེད། དེ་ནས་ result.json ཡིག་ཆ་འདེམས། ཡང་ན་དེའི་ཡི་གེ་སྦྱར། ཁ་བརྡ་རེ་རེ་ Direct messages དང་ Groups ཡང་ན་ Channels ནང་ཤོག་བྱང་གཅིག་ཏུ་འགྱུར། དེའི་འཕྲིན་ཡིག་རྣམས་ཤོག་བྱང་གི་བསམ་ཚུལ་དུ་འགྱུར་བས་ Chat མཐོང་སྣང་གིས་ཁ་བརྡ་སྟོན། པར་དང་ཡིག་ཆ་ནང་འདྲེན་མི་བྱེད།",
"import-board-instruction-whatsapp": "WhatsApp ནང་ཁ་བརྡ་ཁ་ཕྱེ། བརྙན་ཆས་མེད་པའི་ Export chat འདེམས། .txt ཡིག་ཆ་འདིར་འདེམས། ཡང་ན་དེའི་ཡི་གེ་སྦྱར། ཁ་བརྡ་དེ་ཤོག་བྱང་གཅིག་ཏུ་འགྱུར་ཞིང་། དེའི་འཕྲིན་ཡིག་རྣམས་གཏོང་མཁན་དང་དུས་ཚོད་བཅས་དེའི་བསམ་ཚུལ་ཡིན་པས་ Chat མཐོང་སྣང་གིས་དེ་སྟོན། བརྙན་ཆས་དང་མ་ལག་གི་འཕྲིན་ཡིག་ནང་འདྲེན་མི་བྱེད།",
"import-board-instruction-discord": "DiscordChatExporter ཡིས་ JSON རྣམ་གཞག་ཐོག་ Discord བརྒྱུད་ལམ་གཅིག་ཕྱིར་འདྲེན་བྱས་ནས་ .json ཡིག་ཆ་འདེམས། ཡང་ན་དེའི་ཡི་གེ་སྦྱར། བརྒྱུད་ལམ་དེ་རང་གི་རིགས་ནང་ཤོག་བྱང་གཅིག་ཏུ་འགྱུར། དེའི་འཕྲིན་ཡིག་རྣམས་ཤོག་བྱང་གི་བསམ་ཚུལ་དུ་འགྱུར་བས་ Chat མཐོང་སྣང་གིས་བརྒྱུད་ལམ་སྟོན། ཞབས་ཞུ་འཕྲུལ་ཆས་ལམ་དུ་འགྱུར། ཟུར་སྦྱར་ནང་འདྲེན་མི་བྱེད།",
"import-board-instruction-rocketchat": "Rocket.Chat ནང་ \"My Data\" ནས་རང་གི་གཞི་གྲངས་ JSON རྣམ་གཞག་ཐོག་ཕྱིར་འདྲེན་བྱས་ནས་དེས་ཁྱེད་ལ་བསྐུར་བའི་ .zip ཡིག་ཆ་འམ་ཁང་མིག་གཅིག་གི་ཕྱིར་འདྲེན་བྱས་པའི་ .json ཡིག་ཆ་འདེམས། ཁང་མིག་རེ་རེ་ཤོག་བྱང་གཅིག་ཏུ་འགྱུར། དེའི་འཕྲིན་ཡིག་རྣམས་ཤོག་བྱང་གི་བསམ་ཚུལ་དུ་འགྱུར་བས་ Chat མཐོང་སྣང་གིས་ཁང་མིག་སྟོན། WeKan གྱིས་ Rocket.Chat ཡི་ CSV ནང་འདྲེན་ཆས་ཆེད་དུ་ཕྱིར་འདྲེན་བྱས་པའི་ .zip ཡང་ཀློག་ཐུབ།",
"import-board-instruction-evernote": "Evernote ནང་ཟིན་བྲིས་སམ་ཟིན་དེབ་གཅིག་ .enex ཡིག་ཆ་ལྟར་ཕྱིར་འདྲེན་བྱས་ནས་འདིར་འདེམས། ཡང་ན་དེའི་ཡི་གེ་སྦྱར། ཟིན་བྲིས་རེ་རེ་དེའི་ཡི་གེ་དང་། ཞིབ་བཤེར་ཐོ་གཞུང་ལྟར་དེའི་བྱ་རིམ་སྒྲོམ། ཁ་བྱང་ལྟར་དེའི་རྟགས། དུས་ཚོད་ཚང་བ་ལྟར་དེའི་དྲན་སྐུལ་བཅས་ཤོག་བྱང་གཅིག་ཏུ་འགྱུར། དྲན་སྐུལ་ལེགས་གྲུབ་བྱུང་བའི་ཟིན་བྲིས་རྣམས་ Done ལ་འགྲོ། པར་རིས་དང་ཟུར་སྦྱར་ཡིག་ཆ་ནང་འདྲེན་མི་བྱེད།",
"tool-group-kanban": "Kanban དང་ལས་གཞིའི་ལག་ཆ",
"tool-group-issues": "གནད་དོན་རྗེས་འདེད་དང་པར་གཞི་དོ་དམ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "E Redmine, digorit Issues ar raktres, dibabit Also available in: CSV e traoñ ar roll, dibabit ar bannoù (All columns, gant Description) hag ezporzhiit, ha pegit ar CSV goude. Redmine a anv ar bannoù en ho yezh, setu lakait ho yezh e saozneg e My account a-raok ezporzhiañ. Pep statud a zeu da vezañ ur roll hag an issues a zeu da vezañ kartennoù, gant an tracker evel tikedenn, den deverket, aozer, deiziadoù, trevell kar hag issues kar; ar briorelezh, ar rummad, ar stumm pal, an amzer priziet, % Done hag ar maeziennoù personelaet a zeu da vezañ maeziennoù personelaet.",
"import-board-instruction-notion": "E Notion, digorit an diaz roadennoù evel ur bajenn a-bezh, dibabit ••• hag Export, dibabit Markdown & CSV, ha dibabit ar restr .zip a vez pellgarget, pe unan eus CSVoù an diaz roadennoù enni, pe pegit ar CSV-se. Ur bann anvet Status a zeu da vezañ ar rolloù (hep anezhañ, ar bann kentañ a seblant bezañ ur select, ha danevell an enporzhiañ a lavar pehini); al linennoù a zeu da vezañ kartennoù gant o zitl, tikedennoù evel tikedennoù, tud evel izili, deiziadoù, ha testenn ar bajenn evel deskrivadur; ar bannoù all a zeu da vezañ maeziennoù personelaet. An darempredoù, ar skeudennoù hag ar stagadennoù n'int ket enporzhiet.",
"import-board-instruction-plane": "E Plane, digorit Workspace Settings, dibabit Exports, ezporzhiit ar raktresoù evel JSON, CSV pe Excel ha pellgargit ar restr .zip, ha dibabit ar restr-se goude, pe ur restr enni, pe pegit ar JSON pe ar CSV. An stadoù a zeu da vezañ rolloù, ar raktresoù a zeu da vezañ bandennoù, hag an issues a zeu da vezañ kartennoù gant o anaouder, kar, tud deverket, tikedennoù, deiziadoù, liammoù hag evezhiadennoù; ar briorelezh, ar briziadenn, ar c'helc'hiad hag ar mollad a zeu da vezañ maeziennoù personelaet. Ezporzhiadur Plane n'en deus deskrivadur na stagadenn ebet, setu n'int ket enporzhiet.",
"import-board-instruction-fizzy": "E Fizzy, ezporzhiit ar gont e «Account settings», pe ho kartennoù deoc'h gant «Download my data», ha dibabit ar restr .zip a gas Fizzy deoc'h, pe restr .json ur gartenn. An taolennoù a zeu da vezañ bandennoù hag ar bannoù a zeu da vezañ rolloù, gant «Maybe?», «Not now» ha «Done» evel e Fizzy; ar c'hartennoù a vir o deskrivadur, o zikedennoù, an dud deverket, ar paziadoù evel ul liskadur, an evezhiadennoù hag ar restroù.",
"import-board-instruction-mail": "Dibabit ur restr .mbox, evel ma vez enrollet gant Thunderbird, Apple Mail, mutt pe Gmail dre Google Takeout, pe ur gemennadenn .eml hepken, pe pegit e destenn. Pep kaozeadenn a zeu da vezañ ur gartenn er roll Inbox, gant he c'haser, he degemererien hag he sujed, evit ma vo diskouezet er gwel Email; ar respontoù a zeu da vezañ he evezhiadennoù. Tikedennoù Gmail a zeu da vezañ tikedennoù. Ar restroù stag n'int ket enporzhiet.",
"import-board-instruction-ical": "Dibabit ur restr deiziadur .ics, evel ma vez ezporzhiet gant Google Calendar, Apple Calendar pe Reminders, Thunderbird, Nextcloud pe Outlook, pe pegit e destenn. An trevelloù a ya da To Do, In Progress, Done pe Cancelled hervez o stad, hag an darvoudoù da Events, gant o deiziadoù kregiñ ha termen, evit ma vint diskouezet er gweloù Calendar ha Gantt. Ar rummadoù hag ar renk a zeu da vezañ tikedennoù. An elfennoù a adc'hoarvez a vez enporzhiet ur wech.",
"import-board-instruction-googletakeout": "War takeout.google.com, dibabit Tasks, Keep, Mail, Calendar ha Google Chat, krouit an ezporzhiadur ha pellgargit ar restr .zip, ha goude dibabit anezhañ amañ. Pep produ a zeu da vezañ ur vandenn: ar postel evit ar gwel Email, ar rolloù trevelloù hag an notennoù gant o liskadurioù, darvoudoù an deiziadur hag an trevelloù gant deiziadoù, hag an egorioù flapañ ma'z eo o c'hemennadennoù evezhiadennoù evit ar gwel Chat. Ar produioù all hag ar restroù stag n'int ket enporzhiet.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "E Telegram Desktop, digorit Settings, Advanced, Export Telegram data, dibabit ar furmad JSON hag ezporzhiit, ha goude dibabit ar restr result.json, pe pegit e destenn. Pep flap a zeu da vezañ ur gartenn e Direct messages, Groups pe Channels, hag e gemennadennoù a zeu da vezañ evezhiadennoù ar gartenn, evit ma ziskouezo ar gwel Chat ar flap. Ar poltredoù hag ar restroù n'int ket enporzhiet.",
"import-board-instruction-whatsapp": "E WhatsApp, digorit ar flap, dibabit Export chat hep media, ha dibabit ar restr .txt amañ, pe pegit e destenn. Ar flap a zeu da vezañ ur gartenn ma'z eo he c'hemennadennoù he evezhiadennoù, gant o c'haser hag o eur, evit ma ziskouezo ar gwel Chat anezhi. Ar media hag ar c'hemennadennoù reizhiad n'int ket enporzhiet.",
"import-board-instruction-discord": "Ezporzhiit ur c'hanol Discord gant DiscordChatExporter er furmad JSON ha dibabit ar restr .json, pe pegit e destenn. Ar c'hanol a zeu da vezañ ur gartenn en e rummad, hag e gemennadennoù a zeu da vezañ evezhiadennoù ar gartenn, evit ma ziskouezo ar gwel Chat ar c'hanol. Ar servijer a zeu da vezañ ar vandenn. Ar restroù stag n'int ket enporzhiet.",
"import-board-instruction-rocketchat": "E Rocket.Chat, ezporzhiit ho roadennoù e JSON e «My Data» ha dibabit ar restr .zip a gas deoc'h, pe restr .json ezporzhiet ur sal. Pep sal a zeu da vezañ ur gartenn hag he c'hemennadennoù a zeu da vezañ evezhiadennoù ar gartenn, evit ma ziskouezo ar gwel Chat ar sal. Lennet e vez ivez ar restr .zip a ezporzh WeKan evit enporzhier CSV Rocket.Chat.",
"import-board-instruction-evernote": "E Evernote, ezporzhiit an notennoù pe ur c'harned evel ur restr .enex ha dibabit anezhañ amañ, pe pegit e destenn. Pep notenn a zeu da vezañ ur gartenn gant he zestenn, he boestoù trevelloù evel ul liskadur, he gerioù-alc'hwez evel tikedennoù hag he degas-soñj evel an termen; an notennoù ma'z eo graet o degas-soñj a ya da Done. Ar skeudennoù hag ar restroù stag n'int ket enporzhiet.",
"tool-group-kanban": "Ostilhoù Kanban ha raktresoù",
"tool-group-issues": "Heulierien kudennoù ha merañ ar stummoù",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "U aplikaciji Redmine otvorite Issues projekta, odaberite Also available in: CSV na dnu liste, izaberite kolone (All columns, uz Description) i izvezite ih, a zatim zalijepite CSV. Redmine naziva kolone na vašem jeziku, pa prije izvoza postavite jezik na English u My account. Svaki status postaje lista, a prijave postaju kartice s vrstom prijave kao oznakom, dodijeljenom osobom, autorom, datumima, nadređenim zadatkom i povezanim prijavama; prioritet, kategorija, ciljna verzija, procijenjeno vrijeme, % Done i prilagođena polja postaju prilagođena polja.",
"import-board-instruction-notion": "U aplikaciji Notion otvorite bazu podataka kao cijelu stranicu, odaberite ••• i Export, izaberite Markdown & CSV i odaberite preuzetu .zip datoteku ili jednu CSV datoteku baze podataka iz nje, ili zalijepite taj CSV. Kolona nazvana Status postaje liste (ako je nema, koristi se prva kolona koja izgleda kao izbor, a izvještaj o uvozu navodi koja); redovi postaju kartice s naslovom, oznakama, osobama kao članovima, datumima i tekstom stranice kao opisom; ostale kolone postaju prilagođena polja. Relacije, slike i prilozi se ne uvoze.",
"import-board-instruction-plane": "U aplikaciji Plane otvorite Workspace Settings, odaberite Exports, izvezite projekte kao JSON, CSV ili Excel i preuzmite .zip datoteku, a zatim odaberite tu datoteku ili jednu datoteku iz nje, ili zalijepite JSON ili CSV. Stanja postaju liste, projekti postaju trake, a prijave postaju kartice s identifikatorom, nadređenom stavkom, dodijeljenim osobama, oznakama, datumima, vezama i komentarima; prioritet, procjena, ciklus i modul postaju prilagođena polja. Izvoz iz aplikacije Plane ne sadrži opise ni priloge, pa se oni ne uvoze.",
"import-board-instruction-fizzy": "U aplikaciji Fizzy izvezite račun u „Account settings“, ili svoje kartice pomoću „Download my data“, i odaberite .zip datoteku koju vam Fizzy pošalje, ili .json datoteku jedne kartice. Table postaju trake, a kolone postaju liste, sa „Maybe?“, „Not now“ i „Done“ kao u aplikaciji Fizzy; kartice zadržavaju svoj opis, oznake, zadužene, korake kao kontrolnu listu, komentare i datoteke.",
"import-board-instruction-mail": "Odaberite .mbox datoteku, kako je spremaju Thunderbird, Apple Mail, mutt ili Gmail putem Google Takeout, ili jednu .eml poruku, ili zalijepite njen tekst. Svaki razgovor postaje jedna kartica u listi Inbox, sa svojim pošiljaocem, primaocima i predmetom, tako da se prikazuje u prikazu Email; odgovori postaju njeni komentari. Gmail oznake postaju oznake. Prilozi se ne uvoze.",
"import-board-instruction-ical": "Odaberite .ics kalendarsku datoteku, kako je izvoze Google Calendar, Apple Calendar ili Reminders, Thunderbird, Nextcloud ili Outlook, ili zalijepite njen tekst. Zadaci idu u To Do, In Progress, Done ili Cancelled prema svom statusu, a događaji u Events, sa svojim datumima početka i dospijeća, tako da se prikazuju u prikazima Calendar i Gantt. Kategorije i prioritet postaju oznake. Stavke koje se ponavljaju uvoze se jednom.",
"import-board-instruction-googletakeout": "Na takeout.google.com odaberite Tasks, Keep, Mail, Calendar i Google Chat, napravite izvoz i preuzmite .zip datoteku, zatim je odaberite ovdje. Svaki proizvod postaje traka: pošta za prikaz Email, liste zadataka i bilješke sa svojim kontrolnim listama, kalendarski događaji i zadaci s datumima, te prostori za razgovor čije su poruke komentari za prikaz Chat. Ostali proizvodi i prilozi se ne uvoze.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "U Telegram Desktop otvorite Settings, Advanced, Export Telegram data, odaberite JSON format i izvezite, zatim odaberite datoteku result.json, ili zalijepite njen tekst. Svaki razgovor postaje kartica u Direct messages, Groups ili Channels, a njegove poruke postaju komentari kartice, tako da prikaz Chat prikazuje razgovor. Fotografije i datoteke se ne uvoze.",
"import-board-instruction-whatsapp": "U WhatsAppu otvorite razgovor, odaberite Export chat bez medija i ovdje odaberite .txt datoteku, ili zalijepite njen tekst. Razgovor postaje kartica čije su poruke njeni komentari, prema pošiljaocu i vremenu, tako da ga prikaz Chat prikazuje. Mediji i sistemske poruke se ne uvoze.",
"import-board-instruction-discord": "Izvezite Discord kanal pomoću DiscordChatExporter u JSON formatu i odaberite .json datoteku, ili zalijepite njen tekst. Kanal postaje kartica u svojoj kategoriji, a njegove poruke postaju komentari kartice, tako da prikaz Chat prikazuje kanal. Server postaje traka. Prilozi se ne uvoze.",
"import-board-instruction-rocketchat": "U aplikaciji Rocket.Chat izvezite svoje podatke kao JSON u „My Data“ i odaberite .zip datoteku koju vam pošalje, ili izvezenu .json datoteku jedne sobe. Svaka soba postaje kartica, a njene poruke postaju komentari kartice, tako da prikaz Chat prikazuje sobu. Čita se i .zip koji WeKan izvozi za CSV uvoznik aplikacije Rocket.Chat.",
"import-board-instruction-evernote": "U Evernoteu izvezite bilješke ili bilježnicu kao .enex datoteku i odaberite je ovdje, ili zalijepite njen tekst. Svaka bilješka postaje kartica sa svojim tekstom, svojim poljima zadataka kao kontrolnom listom, svojim tagovima kao oznakama i svojim podsjetnikom kao datumom dospijeća; bilješke čiji je podsjetnik završen idu u Done. Slike i priložene datoteke se ne uvoze.",
"tool-group-kanban": "Kanban i alati za projekte",
"tool-group-issues": "Praćenje problema i kontrola verzija",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine дээрэ түсэлэй Issues нээжэ, жагсаалай доодо талада Also available in: CSV шэлэгты, багананууд шэлээд (All columns, Description-тэй) гаргагты, тиигээд CSV оруулагты. Redmine багануудые таанарай хэлэн дээрэ нэрлэдэг тула гаргахаһаа урда My account соо хэлээ англи болгогты. Байдал бүхэн жагсаал болоно, асуудалнууд tracker-ые тэмдэг болгон, хариуцагша, автор, үдэрнүүд, эхэ даабари болон холбогдохо асуудалнуудтаяа карточка болоно; шухалын зэргэ, ангилал, зорилгын хэлбэри, тооссон саг, % Done болон тусхай талмайнууд тусхай талмай болоно.",
"import-board-instruction-notion": "Notion дээрэ мэдээсэлэй баазые бүтэн хуудаһан болгожо нээгээд, ••• болон Export шэлэжэ, Markdown & CSV шэлээд, буулгагдаһан .zip файл, али тэрэнэй соохи нэгэ мэдээсэлэй баазын CSV шэлэгты, али тэрэ CSV оруулагты. Status гэһэн нэрэтэй багана жагсаал болоно (үгы һаа, шэлэлгэ шэнги түрүүшын багана болоно, оруулгын тайлан аль багана гэжэ хэлэнэ); мүрнүүд нэрэ, тагуудаа тэмдэг болгон, хүнүүдые гэшүүн болгон, үдэрнүүд болон хуудаһанай текстые тодорхойлго болгон карточка болоно; бусад багананууд тусхай талмай болоно. Холбоонууд, зурагууд болон хабсаргалтанууд оруулагдахагүй.",
"import-board-instruction-plane": "Plane дээрэ Workspace Settings нээжэ, Exports шэлээд, түсэлнүүдые JSON, CSV али Excel болгожо гаргаад .zip файл буулгагты, тиигээд тэрэ файл, али соохи нэгэ файл шэлэгты, али JSON али CSV оруулагты. Байдалнууд жагсаал, түсэлнүүд зурбаһа, асуудалнууд тэмдэглэгшэ, эхэ, хариуцагшад, тэмдэгүүд, үдэрнүүд, холбоосууд болон тайлбаринуудтаяа карточка болоно; шухалын зэргэ, тооссоо, цикл болон модуль тусхай талмай болоно. Plane-ай экспорт соо тодорхойлго али хабсаргалта үгы тула оруулагдахагүй.",
"import-board-instruction-fizzy": "Fizzy соо дансые «Account settings» хэһэгтэ, али өөрынгөө карточкануудые «Download my data»-аар экспортлоод, Fizzy-гэй танда эльгээһэн .zip файл, али нэгэ карточкын .json файл шэлэгты. Самбарнууд замууд болоно, баганануудынь жагсаалтанууд болоно, «Maybe?», «Not now» болон «Done» Fizzy соохитой адли; карточканууд өөрынгөө тайлбари, тэмдэгүүд, харюусалгатанууд, алхамуудые шалгалтын жагсаалта болгон, һанамжанууд болон файлнуудаа хадагална.",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt гү, али Google Takeout-аар Gmail хадагалдаг .mbox файл, али нэгэ .eml бэшэг шэлэгты, али түүнэй бэшэг табигты. Һэн бүхэн хөөрэлдөөн эльгээгшэ, абагшад болон гаршагтаяа Inbox жагсаалтада нэгэ карточка болоно, тиимэһээ Email харагдалта дээрэ харагдана; харюунууд түүнэй һанамжанууд болоно. Gmail тэмдэгүүд тэмдэгүүд болоно. Хабсаргалганууд оруулагдахагүй.",
"import-board-instruction-ical": "Google Calendar, Apple Calendar гү, али Reminders, Thunderbird, Nextcloud гү, али Outlook гаргадаг .ics хуанлиин файл шэлэгты, али түүнэй бэшэг табигты. Даабаринууд байдалаараа To Do, In Progress, Done гү, али Cancelled руу, үйлэ ябадалнууд Events руу эхилхэ болон дүүргэхэ үдэрнүүдтэйгээ ошоно, тиимэһээ Calendar болон Gantt харагдалтануудта харагдана. Ангинууд болон эрхимлэл тэмдэгүүд болоно. Дабтагдадаг зүйлнүүд нэгэ дахин оруулагдана.",
"import-board-instruction-googletakeout": "takeout.google.com дээрэ Tasks, Keep, Mail, Calendar болон Google Chat шэлэжэ, экспорт хэжэ .zip файл буулгагты, удаань эндэ шэлэгты. Һэн бүхэн бүтээгдэхүүн зам болоно: Email харагдалтада бэшэгүүд, шалгалтын жагсаалтануудтайгаа даабаринуудай жагсаалтанууд ба тэмдэглэлнүүд, үдэрнүүдтэй хуанлиин үйлэ ябадалнууд ба даабаринууд, бэшэгүүдынь Chat харагдалтада һанамжанууд болодог чатай газарнууд. Бусад бүтээгдэхүүнүүд болон хабсаргалганууд оруулагдахагүй.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-то Settings, Advanced, Export Telegram data нээжэ, JSON хэлбэри шэлэжэ экспортлоод, удаань result.json файл шэлэгты, али түүнэй бэшэг табигты. Һэн бүхэн чат Direct messages, Groups гү, али Channels соо карточка болоно, түүнэй бэшэгүүд карточкын һанамжанууд болоно, тиимэһээ Chat харагдалта чатые харуулна. Фото зурагууд болон файлнууд оруулагдахагүй.",
"import-board-instruction-whatsapp": "WhatsApp-та чатые нээжэ, медиагүйгөөр Export chat шэлэжэ, .txt файлые эндэ шэлэгты, али түүнэй бэшэг табигты. Чат бэшэгүүдынь эльгээгшэ болон сагаараа түүнэй һанамжанууд болодог карточка болоно, тиимэһээ Chat харагдалта үүниие харуулна. Медиа болон системын бэшэгүүд оруулагдахагүй.",
"import-board-instruction-discord": "Discord каналые DiscordChatExporter-аар JSON хэлбэридэ экспортлоод .json файл шэлэгты, али түүнэй бэшэг табигты. Канал өөрынгөө ангида карточка болоно, түүнэй бэшэгүүд карточкын һанамжанууд болоно, тиимэһээ Chat харагдалта каналые харуулна. Сервер зам болоно. Хабсаргалганууд оруулагдахагүй.",
"import-board-instruction-rocketchat": "Rocket.Chat соо өөрынгөө мэдээсэлые «My Data» хэһэгтэ JSON хэлбэридэ экспортлоод, танда эльгээһэн .zip файл, али нэгэ таһалгын экспортлогдоһон .json файл шэлэгты. Таһалга бүхэн карточка болоно, түүнэй бэшэгүүд карточкын һанамжанууд болоно, тиимэһээ Chat харагдалта таһалгые харуулна. WeKan-ай Rocket.Chat-ай CSV импортлогшодо экспортлодог .zip мөн уншагдана.",
"import-board-instruction-evernote": "Evernote-то тэмдэглэлнүүд гү, али тэмдэглэлэй дэбтэрые .enex файл болгон экспортлоод эндэ шэлэгты, али түүнэй бэшэг табигты. Һэн бүхэн тэмдэглэл бэшэгээрээ, шалгалтын жагсаалта болгон даабаринуудай хайрсагуудаараа, тэмдэгүүд болгон тагуудаараа, дүүргэхэ үдэр болгон һануулгаараа карточка болоно; һануулгань дүүргэгдэһэн тэмдэглэлнүүд Done руу ошоно. Зурагууд болон хабсаргагдаһан файлнууд оруулагдахагүй.",
"tool-group-kanban": "Канбан ба түсэлэй хэрэгсэлнүүд",
"tool-group-issues": "Асуудал хинагшад ба хубилбари хиналта",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "A Redmine, obriu Issues del projecte, trieu Also available in: CSV al final de la llista, seleccioneu les columnes (All columns, amb Description) i exporteu; després enganxeu el CSV. Redmine posa els noms de les columnes en la vostra llengua, així que abans d’exportar establiu la llengua English a My account. Cada estat esdevé una llista i les incidències esdevenen fitxes, amb el tipus d’incidència com a etiqueta, persona assignada, autor, dates, tasca principal i incidències relacionades; la prioritat, categoria, versió de destinació, temps estimat, % Done i camps personalitzats esdevenen camps personalitzats.",
"import-board-instruction-notion": "A Notion, obriu la base de dades com a pàgina completa, trieu ••• i Export, seleccioneu Markdown & CSV i trieu el fitxer .zip descarregat, o un CSV de base de dades que contingui, o enganxeu aquest CSV. Una columna anomenada Status esdevé les llistes (si no n’hi ha, s’utilitza la primera columna que sembla un camp de selecció, i l’informe d’importació indica quina); les files esdevenen fitxes amb el títol, etiquetes, persones com a membres, dates i el text de la pàgina com a descripció; les altres columnes esdevenen camps personalitzats. Les relacions, imatges i fitxers adjunts no s’importen.",
"import-board-instruction-plane": "A Plane, obriu Workspace Settings, trieu Exports, exporteu els projectes en format JSON, CSV o Excel i descarregueu el fitxer .zip; després seleccioneu aquest fitxer, o un dels fitxers que conté, o enganxeu el JSON o CSV. Els estats esdevenen llistes, els projectes esdevenen carrils i les incidències esdevenen fitxes amb l’identificador, element principal, persones assignades, etiquetes, dates, enllaços i comentaris; la prioritat, estimació, cicle i mòdul esdevenen camps personalitzats. L’exportació de Plane no conté descripcions ni fitxers adjunts, de manera que no s’importen.",
"import-board-instruction-fizzy": "A Fizzy, exporta el compte a «Account settings», o les teves pròpies fitxes amb «Download my data», i tria el fitxer .zip que t'envia Fizzy, o el fitxer .json d'una fitxa. Els taulers es converteixen en carrils i les columnes en llistes, amb «Maybe?», «Not now» i «Done» com a Fizzy; les fitxes conserven la descripció, les etiquetes, les persones assignades, els passos com a llista de verificació, els comentaris i els fitxers.",
"import-board-instruction-mail": "Tria un fitxer .mbox, tal com el desen Thunderbird, Apple Mail, mutt o Gmail a través de Google Takeout, o un sol missatge .eml, o enganxa'n el text. Cada conversa es converteix en una fitxa a la llista Inbox, amb el seu remitent, destinataris i assumpte, perquè es mostri a la vista Email; les respostes es converteixen en els seus comentaris. Les etiquetes de Gmail es converteixen en etiquetes. Els adjunts no s'importen.",
"import-board-instruction-ical": "Tria un fitxer de calendari .ics, tal com l'exporten Google Calendar, Apple Calendar o Reminders, Thunderbird, Nextcloud o Outlook, o enganxa'n el text. Les tasques van a To Do, In Progress, Done o Cancelled segons el seu estat, i els esdeveniments a Events, amb les seves dates d'inici i de venciment, perquè es mostrin a les vistes Calendar i Gantt. Les categories i la prioritat es converteixen en etiquetes. Els elements que es repeteixen s'importen una vegada.",
"import-board-instruction-googletakeout": "A takeout.google.com, tria Tasks, Keep, Mail, Calendar i Google Chat, crea l'exportació i baixa el fitxer .zip, després tria'l aquí. Cada producte es converteix en un carril: el correu per a la vista Email, les llistes de tasques i les notes amb les seves llistes de verificació, els esdeveniments del calendari i les tasques amb dates, i els espais de xat els missatges dels quals són comentaris per a la vista Chat. Altres productes i els adjunts no s'importen.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "A Telegram Desktop, obre Settings, Advanced, Export Telegram data, tria el format JSON i exporta, després tria el fitxer result.json, o enganxa'n el text. Cada xat es converteix en una fitxa a Direct messages, Groups o Channels, i els seus missatges es converteixen en els comentaris de la fitxa, perquè la vista Chat mostri el xat. Les fotos i els fitxers no s'importen.",
"import-board-instruction-whatsapp": "A WhatsApp, obre el xat, tria Export chat sense multimèdia, i tria aquí el fitxer .txt, o enganxa'n el text. El xat es converteix en una fitxa els missatges de la qual són els seus comentaris, pel seu remitent i hora, perquè la vista Chat el mostri. Els elements multimèdia i els missatges del sistema no s'importen.",
"import-board-instruction-discord": "Exporta un canal de Discord amb DiscordChatExporter en format JSON i tria el fitxer .json, o enganxa'n el text. El canal es converteix en una fitxa a la seva categoria, i els seus missatges es converteixen en els comentaris de la fitxa, perquè la vista Chat mostri el canal. El servidor es converteix en el carril. Els adjunts no s'importen.",
"import-board-instruction-rocketchat": "A Rocket.Chat, exporta les teves dades com a JSON a «My Data» i tria el fitxer .zip que t'envia, o el fitxer .json exportat d'una sala. Cada sala es converteix en una fitxa i els seus missatges es converteixen en els comentaris de la fitxa, perquè la vista Chat mostri la sala. També es llegeix el .zip que WeKan exporta per a l'importador CSV de Rocket.Chat.",
"import-board-instruction-evernote": "A Evernote, exporta les notes o una llibreta com a fitxer .enex i tria'l aquí, o enganxa'n el text. Cada nota es converteix en una fitxa amb el seu text, les seves caselles de tasques com a llista de verificació, les seves etiquetes com a etiquetes i el seu recordatori com a data de venciment; les notes amb el recordatori fet van a Done. Les imatges i els fitxers adjunts no s'importen.",
"tool-group-kanban": "Eines Kanban i de projectes",
"tool-group-issues": "Seguiment d'incidències i control de versions",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "A Redmine, obriu Issues del projecte, trieu Also available in: CSV al final de la llista, seleccioneu les columnes (All columns, amb Description) i exporteu; després enganxeu el CSV. Redmine posa els noms de les columnes en la vostra llengua, així que abans d’exportar establiu la llengua English a My account. Cada estat esdevé una llista i les incidències esdevenen fitxes, amb el tipus d’incidència com a etiqueta, persona assignada, autor, dates, tasca principal i incidències relacionades; la prioritat, categoria, versió de destinació, temps estimat, % Done i camps personalitzats esdevenen camps personalitzats.",
"import-board-instruction-notion": "A Notion, obriu la base de dades com a pàgina completa, trieu ••• i Export, seleccioneu Markdown & CSV i trieu el fitxer .zip descarregat, o un CSV de base de dades que continga, o enganxeu este CSV. Una columna anomenada Status esdevé les llistes (si no n’hi ha, s’utilitza la primera columna que sembla un camp de selecció, i l’informe d’importació indica quina); les files esdevenen fitxes amb el títol, etiquetes, persones com a membres, dates i el text de la pàgina com a descripció; les altres columnes esdevenen camps personalitzats. Les relacions, imatges i fitxers adjunts no s’importen.",
"import-board-instruction-plane": "A Plane, obriu Workspace Settings, trieu Exports, exporteu els projectes en format JSON, CSV o Excel i descarregueu el fitxer .zip; després seleccioneu este fitxer, o un dels fitxers que conté, o enganxeu el JSON o CSV. Els estats esdevenen llistes, els projectes esdevenen carrils i les incidències esdevenen fitxes amb l’identificador, element principal, persones assignades, etiquetes, dates, enllaços i comentaris; la prioritat, estimació, cicle i mòdul esdevenen camps personalitzats. L’exportació de Plane no conté descripcions ni fitxers adjunts, de manera que no s’importen.",
"import-board-instruction-fizzy": "A Fizzy, exporta el compte a «Account settings», o les teues pròpies fitxes amb «Download my data», i tria el fitxer .zip que t'envia Fizzy, o el fitxer .json d'una fitxa. Els taulers es convertixen en carrils i les columnes en llistes, amb «Maybe?», «Not now» i «Done» com a Fizzy; les fitxes conserven la descripció, les etiquetes, les persones assignades, els passos com a llista de verificació, els comentaris i els fitxers.",
"import-board-instruction-mail": "Tria un fitxer .mbox, tal com el desen Thunderbird, Apple Mail, mutt o Gmail a través de Google Takeout, o un sol missatge .eml, o enganxa'n el text. Cada conversa es convertix en una fitxa a la llista Inbox, amb el seu remitent, destinataris i assumpte, perquè es mostre a la vista Email; les respostes es convertixen en els seus comentaris. Les etiquetes de Gmail es convertixen en etiquetes. Els adjunts no s'importen.",
"import-board-instruction-ical": "Tria un fitxer de calendari .ics, tal com l'exporten Google Calendar, Apple Calendar o Reminders, Thunderbird, Nextcloud o Outlook, o enganxa'n el text. Les tasques van a To Do, In Progress, Done o Cancelled segons el seu estat, i els esdeveniments a Events, amb les seues dates d'inici i de venciment, perquè es mostren a les vistes Calendar i Gantt. Les categories i la prioritat es convertixen en etiquetes. Els elements que es repetixen s'importen una vegada.",
"import-board-instruction-googletakeout": "A takeout.google.com, tria Tasks, Keep, Mail, Calendar i Google Chat, crea l'exportació i descarrega el fitxer .zip, després tria'l ací. Cada producte es convertix en un carril: el correu per a la vista Email, les llistes de tasques i les notes amb les seues llistes de verificació, els esdeveniments del calendari i les tasques amb dates, i els espais de xat els missatges dels quals són comentaris per a la vista Chat. Altres productes i els adjunts no s'importen.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "A Telegram Desktop, obre Settings, Advanced, Export Telegram data, tria el format JSON i exporta, després tria el fitxer result.json, o enganxa'n el text. Cada xat es convertix en una fitxa a Direct messages, Groups o Channels, i els seus missatges es convertixen en els comentaris de la fitxa, perquè la vista Chat mostre el xat. Les fotos i els fitxers no s'importen.",
"import-board-instruction-whatsapp": "A WhatsApp, obre el xat, tria Export chat sense multimèdia, i tria ací el fitxer .txt, o enganxa'n el text. El xat es convertix en una fitxa els missatges de la qual són els seus comentaris, pel seu remitent i hora, perquè la vista Chat el mostre. Els elements multimèdia i els missatges del sistema no s'importen.",
"import-board-instruction-discord": "Exporta un canal de Discord amb DiscordChatExporter en format JSON i tria el fitxer .json, o enganxa'n el text. El canal es convertix en una fitxa a la seva categoria, i els seus missatges es convertixen en els comentaris de la fitxa, perquè la vista Chat mostre el canal. El servidor es convertix en el carril. Els adjunts no s'importen.",
"import-board-instruction-rocketchat": "A Rocket.Chat, exporta les teues dades com a JSON a «My Data» i tria el fitxer .zip que t'envia, o el fitxer .json exportat d'una sala. Cada sala es convertix en una fitxa i els seus missatges es convertixen en els comentaris de la fitxa, perquè la vista Chat mostre la sala. També es llig el .zip que WeKan exporta per a l'importador CSV de Rocket.Chat.",
"import-board-instruction-evernote": "A Evernote, exporta les notes o una llibreta com a fitxer .enex i tria'l ací, o enganxa'n el text. Cada nota es convertix en una fitxa amb el seu text, les seues caselles de tasques com a llista de verificació, les seues etiquetes com a etiquetes i el seu recordatori com a data de venciment; les notes amb el recordatori fet van a Done. Les imatges i els fitxers adjunts no s'importen.",
"tool-group-kanban": "Ferramentes Kanban i de projectes",
"tool-group-issues": "Seguiment d'incidències i control de versions",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "A Redmine, obriu Issues del projecte, trieu Also available in: CSV al final de la llista, seleccioneu les columnes (All columns, amb Description) i exporteu; després enganxeu el CSV. Redmine posa els noms de les columnes en la vostra llengua, així que abans d’exportar establiu la llengua English a My account. Cada estat esdevé una llista i les incidències esdevenen fitxes, amb el tipus d’incidència com a etiqueta, persona assignada, autor, dates, tasca principal i incidències relacionades; la prioritat, categoria, versió de destinació, temps estimat, % Done i camps personalitzats esdevenen camps personalitzats.",
"import-board-instruction-notion": "A Notion, obriu la base de dades com a pàgina completa, trieu ••• i Export, seleccioneu Markdown & CSV i trieu el fitxer .zip descarregat, o un CSV de base de dades que contingui, o enganxeu aquest CSV. Una columna anomenada Status esdevé les llistes (si no n’hi ha, s’utilitza la primera columna que sembla un camp de selecció, i l’informe d’importació indica quina); les files esdevenen fitxes amb el títol, etiquetes, persones com a membres, dates i el text de la pàgina com a descripció; les altres columnes esdevenen camps personalitzats. Les relacions, imatges i fitxers adjunts no s’importen.",
"import-board-instruction-plane": "A Plane, obriu Workspace Settings, trieu Exports, exporteu els projectes en format JSON, CSV o Excel i descarregueu el fitxer .zip; després seleccioneu aquest fitxer, o un dels fitxers que conté, o enganxeu el JSON o CSV. Els estats esdevenen llistes, els projectes esdevenen carrils i les incidències esdevenen fitxes amb l’identificador, element principal, persones assignades, etiquetes, dates, enllaços i comentaris; la prioritat, estimació, cicle i mòdul esdevenen camps personalitzats. L’exportació de Plane no conté descripcions ni fitxers adjunts, de manera que no s’importen.",
"import-board-instruction-fizzy": "A Fizzy, exporta el compte a «Account settings», o les teves pròpies fitxes amb «Download my data», i tria el fitxer .zip que t'envia Fizzy, o el fitxer .json d'una fitxa. Els taulers es converteixen en carrils i les columnes en llistes, amb «Maybe?», «Not now» i «Done» com a Fizzy; les fitxes conserven la descripció, les etiquetes, les persones assignades, els passos com a llista de verificació, els comentaris i els fitxers.",
"import-board-instruction-mail": "Tria un fitxer .mbox, tal com el desen Thunderbird, Apple Mail, mutt o Gmail a través de Google Takeout, o un sol missatge .eml, o enganxa'n el text. Cada conversa es converteix en una fitxa a la llista Inbox, amb el seu remitent, destinataris i assumpte, perquè es mostri a la vista Email; les respostes es converteixen en els seus comentaris. Les etiquetes de Gmail es converteixen en etiquetes. Els adjunts no s'importen.",
"import-board-instruction-ical": "Tria un fitxer de calendari .ics, tal com l'exporten Google Calendar, Apple Calendar o Reminders, Thunderbird, Nextcloud o Outlook, o enganxa'n el text. Les tasques van a To Do, In Progress, Done o Cancelled segons el seu estat, i els esdeveniments a Events, amb les seves dates d'inici i de venciment, perquè es mostrin a les vistes Calendar i Gantt. Les categories i la prioritat es converteixen en etiquetes. Els elements que es repeteixen s'importen una vegada.",
"import-board-instruction-googletakeout": "A takeout.google.com, tria Tasks, Keep, Mail, Calendar i Google Chat, crea l'exportació i baixa el fitxer .zip, després tria'l aquí. Cada producte es converteix en un carril: el correu per a la vista Email, les llistes de tasques i les notes amb les seves llistes de verificació, els esdeveniments del calendari i les tasques amb dates, i els espais de xat els missatges dels quals són comentaris per a la vista Chat. Altres productes i els adjunts no s'importen.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "A Telegram Desktop, obre Settings, Advanced, Export Telegram data, tria el format JSON i exporta, després tria el fitxer result.json, o enganxa'n el text. Cada xat es converteix en una fitxa a Direct messages, Groups o Channels, i els seus missatges es converteixen en els comentaris de la fitxa, perquè la vista Chat mostri el xat. Les fotos i els fitxers no s'importen.",
"import-board-instruction-whatsapp": "A WhatsApp, obre el xat, tria Export chat sense multimèdia, i tria aquí el fitxer .txt, o enganxa'n el text. El xat es converteix en una fitxa els missatges de la qual són els seus comentaris, pel seu remitent i hora, perquè la vista Chat el mostri. Els elements multimèdia i els missatges del sistema no s'importen.",
"import-board-instruction-discord": "Exporta un canal de Discord amb DiscordChatExporter en format JSON i tria el fitxer .json, o enganxa'n el text. El canal es converteix en una fitxa a la seva categoria, i els seus missatges es converteixen en els comentaris de la fitxa, perquè la vista Chat mostri el canal. El servidor es converteix en el carril. Els adjunts no s'importen.",
"import-board-instruction-rocketchat": "A Rocket.Chat, exporta les teves dades com a JSON a «My Data» i tria el fitxer .zip que t'envia, o el fitxer .json exportat d'una sala. Cada sala es converteix en una fitxa i els seus missatges es converteixen en els comentaris de la fitxa, perquè la vista Chat mostri la sala. També es llegeix el .zip que WeKan exporta per a l'importador CSV de Rocket.Chat.",
"import-board-instruction-evernote": "A Evernote, exporta les notes o una llibreta com a fitxer .enex i tria'l aquí, o enganxa'n el text. Cada nota es converteix en una fitxa amb el seu text, les seves caselles de tasques com a llista de verificació, les seves etiquetes com a etiquetes i el seu recordatori com a data de venciment; les notes amb el recordatori fet van a Done. Les imatges i els fitxers adjunts no s'importen.",
"tool-group-kanban": "Eines Kanban i de projectes",
"tool-group-issues": "Seguiment d'incidències i control de versions",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine ᎠᏂ, ᏗᎦᎸᏫᏍᏓᏁᏗ Issues ᎯᏍᏚᎢᏍᏓ, Also available in: CSV ᎠᏎᏊᎢ ᎡᎳᏗᏢ ᎯᏑᏰᏍᏓ, ᏗᏍᏓᏯ ᎯᏑᏰᏍᏓ (All columns, Description ᎬᏗ) ᎠᎴ ᎭᏓᏅᏍᏓ, ᎿᏉ CSV ᎯᏂᏴ. Redmine ᏗᏍᏓᏯ ᏣᏤᎵ ᎦᏬᏂᎯᏍᏗ ᏚᏙᎥᏍᎪ, ᎾᏍᎩ ᎢᏳᏍᏗ My account ᎠᏂ ᏣᏤᎵ ᎦᏬᏂᎯᏍᏗ ᏲᏁᎦ ᎯᏁᏟᏴᏓ ᎠᏏᏉ ᏂᎭᏓᏅᏍᏗᏍᎬᎾ. ᏂᎦᏛ ᎨᏒ ᎠᏎᏊᎢ ᏂᎦᎵᏍᏗᏍᎪ ᎠᎴ ᏗᎦᎸᏫᏍᏓᏁᏗ ᏗᎪᏪᎵ ᏂᎦᎵᏍᏗᏍᎪ, tracker ᎪᏪᎳᏅᎯ, ᏗᎦᎸᏫᏍᏓᏁᎯ, ᎤᏬᏪᎳᏅ, ᎢᎦ, ᎤᏂᏍᏗ ᎦᎸᏫᏍᏓᏁᏗ ᎠᎴ ᏓᏓᏙᏓᏅ ᏗᎦᎸᏫᏍᏓᏁᏗ ᎬᏗ; ᎢᎬᏱᏗᏢ, ᎤᏍᏗ ᏗᏟᏍᏗ, target version, estimated time, % Done ᎠᎴ ᎤᏤᎵ ᏗᎦᏙᎯ ᎤᏤᎵ ᏗᎦᏙᎯ ᏂᎦᎵᏍᏗᏍᎪ.",
"import-board-instruction-notion": "Notion ᎠᏂ, ᏗᎦᎦᏙᏍᏙᏗ ᏂᎦᏛ ᎪᏪᎵ ᎯᏍᏚᎢᏍᏓ, ••• ᎠᎴ Export ᎯᏑᏰᏍᏓ, Markdown & CSV ᎯᏑᏰᏍᏓ, ᎠᎴ .zip ᎪᏪᎸ ᎡᎳᏗ ᎦᏐᏅᏍᏔᏅ ᎯᏑᏰᏍᏓ, ᎠᎴᏉ ᏌᏊ CSV ᎾᎿ ᏓᏓᏁᎸ, ᎠᎴᏉ ᎾᏍᎩ CSV ᎯᏂᏴ. Status ᏧᏙᎢᏛ ᎠᏍᏓᏯ ᏗᎠᏎᏊᎢ ᏂᎦᎵᏍᏗᏍᎪ (ᎢᏳᏃ Ꮭ ᏱᎩ, ᎢᎬᏱ ᎠᏍᏓᏯ select ᏥᏄᏍᏗ ᎾᏍᎩ ᏂᎦᎵᏍᏗᏍᎪ, ᎠᎴ ᎦᏴᏔᏗ ᎧᏃᎮᏛ ᎦᏛᎬᎦ); ᏗᏍᏓᏩᏛᏍᏙᏗ ᏗᎪᏪᎵ ᏂᎦᎵᏍᏗᏍᎪ ᏚᏙᎥ, ᏗᎪᏪᎳᏅᎯ, ᏴᏫ ᎠᏂᎳᏫᏍᎩ, ᎢᎦ, ᎠᎴ ᎪᏪᎵ ᎦᏁᏌᎢ ᎧᏃᎮᏗ ᎬᏗ; ᏅᏩᏓᎴ ᏗᏍᏓᏯ ᎤᏤᎵ ᏗᎦᏙᎯ ᏂᎦᎵᏍᏗᏍᎪ. Relations, ᏗᏟᎶᏍᏙᏗ ᎠᎴ ᏗᏓᏁᏥ Ꮭ ᏱᏓᏴᏔᏂ.",
"import-board-instruction-plane": "Plane ᎠᏂ, Workspace Settings ᎯᏍᏚᎢᏍᏓ, Exports ᎯᏑᏰᏍᏓ, ᏗᎦᎸᏫᏍᏓᏁᏗ JSON, CSV ᎠᎴᏉ Excel ᎭᏓᏅᏍᏓ ᎠᎴ .zip ᎪᏪᎸ ᎡᎳᏗ ᎯᏐᏅᏍᏓ, ᎿᏉ ᎾᏍᎩ ᎪᏪᎸ ᎯᏑᏰᏍᏓ, ᎠᎴᏉ ᏌᏊ ᎪᏪᎸ ᎭᏫᏂ, ᎠᎴᏉ JSON ᎠᎴᏉ CSV ᎯᏂᏴ. ᎨᏒ ᏗᎠᏎᏊᎢ ᏂᎦᎵᏍᏗᏍᎪ, ᏗᎦᎸᏫᏍᏓᏁᏗ ᏓᏅᏃᎯ ᏂᎦᎵᏍᏗᏍᎪ, ᎠᎴ issues ᏗᎪᏪᎵ ᏂᎦᎵᏍᏗᏍᎪ ᏚᏙᎥ, ᎤᏂᏍᏗ, ᏗᎦᎸᏫᏍᏓᏁᎯ, ᏗᎪᏪᎳᏅᎯ, ᎢᎦ, ᏗᏓᏙᏓᏍᏗ ᎠᎴ ᎧᏁᏨᎯ ᎬᏗ; ᎢᎬᏱᏗᏢ, ᎠᏟᎶᏛ, cycle ᎠᎴ module ᎤᏤᎵ ᏗᎦᏙᎯ ᏂᎦᎵᏍᏗᏍᎪ. Plane ᎤᏓᏅᏍᏗ ᎧᏃᎮᏗ ᎠᎴ ᏗᏓᏁᏥ Ꮭ ᏱᏓᏯᎢ, ᎾᏍᎩ ᎢᏳᏍᏗ Ꮭ ᏱᏓᏴᏔᏂ.",
"import-board-instruction-fizzy": "Fizzy ᎠᏂ, \"Account settings\" ᎠᏂ ᎪᏪᎵ ᎯᏄᎪᏫᏒ, ᎠᎴ ᏨᏒ ᏗᎪᏪᎵ \"Download my data\" ᎬᏗ, ᎠᎴ .zip ᎪᏪᎵ Fizzy ᏣᏅᏍᏗ ᏑᏰᏍᎦ, ᎠᎴ ᏌᏉ ᎪᏪᎵ .json ᎪᏪᎵ. ᏗᏟᎶᏍᏙᏗ ᏓᏅᏃᎯ ᎢᎬᏁᏗ ᎠᎴ ᏗᎦᏙᎬ ᏗᎠᏎᏊᎢ ᎢᎬᏁᏗ, \"Maybe?\", \"Not now\" ᎠᎴ \"Done\" Fizzy ᎾᏍᎩᏯ; ᏗᎪᏪᎵ ᏓᏂᏍᏆᏂᎪᏗ ᎤᏂᏤᎵ ᎧᏃᎮᏗ, ᏗᎪᏪᎳᏅᎯ, ᎠᏥᏁᏤᎸ, ᏗᎪᎵᏰᏗ ᏗᎠᏎᏊᎢ ᎾᏍᎩᏯ ᏗᏓᏅᏍᏗ, ᏗᎯᏬᏂᎯᏍᏗ ᎠᎴ ᏗᎪᏪᎵ.",
"import-board-instruction-mail": ".mbox ᎪᏪᎵ ᏑᏰᏍᎦ, Thunderbird, Apple Mail, mutt ᎠᎴ Gmail Google Takeout ᎬᏗ ᎤᏍᏆᏂᎪᏙᏗ ᎾᏍᎩᏯ, ᎠᎴ ᏌᏉ .eml ᎧᏃᎮᏛ, ᎠᎴ ᎾᏍᎩ ᏗᎪᏪᎵ ᎯᏯᏝᏅ. ᏂᎦᏛ ᎧᏃᎮᏛ ᏌᏉ ᎪᏪᎵ ᎢᎬᏁᏗ Inbox ᏗᎠᏎᏊᎢ ᎠᏂ, ᎠᏅᏍᎦ, ᎠᏂᏓᏂᎸᎪ ᎠᎴ ᎦᏛᎬ ᎢᏧᎳᎭ, Email ᏗᎦᏙᏗ ᎤᎾᏄᎪᏫᏍᏗ; ᎠᏂᏁᏤᎲ ᎤᏤᎵ ᏗᎯᏬᏂᎯᏍᏗ ᎢᎬᏁᏗ. Gmail ᏗᎪᏪᎳᏅᎯ ᏗᎪᏪᎳᏅᎯ ᎢᎬᏁᏗ. ᏗᏓᏠᎯᏍᏗ ᎥᏝ ᏴᏫᏗᏓᏍᏗ.",
"import-board-instruction-ical": ".ics ᎢᎦ ᏗᎪᏪᎵ ᏑᏰᏍᎦ, Google Calendar, Apple Calendar ᎠᎴ Reminders, Thunderbird, Nextcloud ᎠᎴ Outlook ᎤᏄᎪᏫᏍᏗ ᎾᏍᎩᏯ, ᎠᎴ ᎾᏍᎩ ᏗᎪᏪᎵ ᎯᏯᏝᏅ. ᏚᎸᏫᏍᏓᏁᎸ To Do, In Progress, Done ᎠᎴ Cancelled ᎠᏂ ᎠᏂᎦᏘᏴ ᏄᎾᏍᏛ ᎢᏳᏍᏗ, ᎠᎴ ᏧᎾᏛᏁᎵᏍᏗ Events ᎠᏂ, ᎤᎾᏓᎴᏅᎯ ᎠᎴ ᎤᎵᏍᏆᏗ ᏗᏙᏓᏆᏍᏗ ᎢᏧᎳᎭ, Calendar ᎠᎴ Gantt ᏗᎦᏙᏗ ᎤᎾᏄᎪᏫᏍᏗ. ᏗᏓᏓᎴᏅᏛ ᎠᎴ ᎢᎬᏱ ᎨᏒ ᏗᎪᏪᎳᏅᎯ ᎢᎬᏁᏗ. ᏔᎵᏁ ᎢᏳᎵᏍᏙᏗ ᏌᏉ ᎢᏳᏓᎴᏅ ᏴᏫᏗᏓᏍᏗ.",
"import-board-instruction-googletakeout": "takeout.google.com ᎠᏂ, Tasks, Keep, Mail, Calendar ᎠᎴ Google Chat ᏑᏰᏍᎦ, ᎤᏄᎪᏫᏍᏗ ᎯᏲᏢ ᎠᎴ .zip ᎪᏪᎵ ᎯᏯᏅ, ᎣᏂ ᎠᏂ ᏑᏰᏍᎦ. ᏂᎦᏛ ᎪᎱᏍᏗ ᏌᏉ ᏓᏅᏃᎯ ᎢᎬᏁᏗ: ᏅᏃᎯ ᎪᏪᎵ Email ᏗᎦᏙᏗ ᏅᏗᎦᎵᏍᏙᏗ, ᏚᎸᏫᏍᏓᏁᎸ ᏗᎠᏎᏊᎢ ᎠᎴ ᏗᎪᏪᎶᏗ ᏗᎪᎵᏰᏗ ᏗᎠᏎᏊᎢ ᎢᏧᎳᎭ, ᎢᎦ ᏗᎪᏪᎵ ᏧᎾᏛᏁᎵᏍᏗ ᎠᎴ ᏚᎸᏫᏍᏓᏁᎸ ᏗᏙᏓᏆᏍᏗ ᎢᏧᎳᎭ, ᎠᎴ ᎦᏬᏂᎯᏍᏗ ᏗᏓᏁᎸ ᎾᏍᎩ ᎤᏂᏃᎮᏛ ᏗᎯᏬᏂᎯᏍᏗ ᎨᏒ Chat ᏗᎦᏙᏗ ᏅᏗᎦᎵᏍᏙᏗ. ᏅᏩᏓᎴ ᎪᎱᏍᏗ ᎠᎴ ᏗᏓᏠᎯᏍᏗ ᎥᏝ ᏴᏫᏗᏓᏍᏗ.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop ᎠᏂ, Settings, Advanced, Export Telegram data ᎯᏍᏚᎢᏒ, JSON ᏄᏍᏛ ᏑᏰᏍᎦ ᎠᎴ ᎯᏄᎪᏫᏒ, ᎣᏂ result.json ᎪᏪᎵ ᏑᏰᏍᎦ, ᎠᎴ ᎾᏍᎩ ᏗᎪᏪᎵ ᎯᏯᏝᏅ. ᏂᎦᏛ ᎦᏬᏂᎯᏍᏗ ᏌᏉ ᎪᏪᎵ ᎢᎬᏁᏗ Direct messages, Groups ᎠᎴ Channels ᎠᏂ, ᎠᎴ ᎤᏤᎵ ᎧᏃᎮᏛ ᎪᏪᎵ ᏗᎯᏬᏂᎯᏍᏗ ᎢᎬᏁᏗ, Chat ᏗᎦᏙᏗ ᎦᏬᏂᎯᏍᏗ ᎤᎾᏄᎪᏫᏍᏗ. ᏗᏟᎶᏍᏔᏅ ᎠᎴ ᏗᎪᏪᎵ ᎥᏝ ᏴᏫᏗᏓᏍᏗ.",
"import-board-instruction-whatsapp": "WhatsApp ᎠᏂ, ᎦᏬᏂᎯᏍᏗ ᎯᏍᏚᎢᏒ, Export chat media ᏂᎨᏒᎾ ᏑᏰᏍᎦ, ᎠᎴ .txt ᎪᏪᎵ ᎠᏂ ᏑᏰᏍᎦ, ᎠᎴ ᎾᏍᎩ ᏗᎪᏪᎵ ᎯᏯᏝᏅ. ᎦᏬᏂᎯᏍᏗ ᏌᏉ ᎪᏪᎵ ᎢᎬᏁᏗ ᎾᏍᎩ ᎤᏤᎵ ᎧᏃᎮᏛ ᏗᎯᏬᏂᎯᏍᏗ ᎨᏒ, ᎠᏅᏍᎦ ᎠᎴ ᎢᏳ ᏅᏗᎦᎵᏍᏙᏗ, Chat ᏗᎦᏙᏗ ᎤᎾᏄᎪᏫᏍᏗ. Media ᎠᎴ ᎪᎱᏍᏗ ᏗᏓᏍᏚᏗ ᎧᏃᎮᏛ ᎥᏝ ᏴᏫᏗᏓᏍᏗ.",
"import-board-instruction-discord": "Discord ᎦᏬᏂᎯᏍᏗ DiscordChatExporter ᎬᏗ JSON ᏄᏍᏛ ᎯᏄᎪᏫᏒ ᎠᎴ .json ᎪᏪᎵ ᏑᏰᏍᎦ, ᎠᎴ ᎾᏍᎩ ᏗᎪᏪᎵ ᎯᏯᏝᏅ. ᎦᏬᏂᎯᏍᏗ ᏌᏉ ᎪᏪᎵ ᎢᎬᏁᏗ ᎤᏤᎵ ᏗᏓᏓᎴᏅᏛ ᎠᏂ, ᎠᎴ ᎤᏤᎵ ᎧᏃᎮᏛ ᎪᏪᎵ ᏗᎯᏬᏂᎯᏍᏗ ᎢᎬᏁᏗ, Chat ᏗᎦᏙᏗ ᎦᏬᏂᎯᏍᏗ ᎤᎾᏄᎪᏫᏍᏗ. Server ᏓᏅᏃᎯ ᎢᎬᏁᏗ. ᏗᏓᏠᎯᏍᏗ ᎥᏝ ᏴᏫᏗᏓᏍᏗ.",
"import-board-instruction-rocketchat": "Rocket.Chat ᎠᏂ, \"My Data\" ᎠᏂ ᏣᏤᎵ ᏗᎪᏪᎵ JSON ᎯᏄᎪᏫᏒ ᎠᎴ .zip ᎪᏪᎵ ᏣᏅᏍᏗ ᏑᏰᏍᎦ, ᎠᎴ ᏌᏉ ᎦᎵᏦᏕ ᎤᏄᎪᏫᏒᎯ .json ᎪᏪᎵ. ᏂᎦᏛ ᎦᎵᏦᏕ ᏌᏉ ᎪᏪᎵ ᎢᎬᏁᏗ ᎠᎴ ᎤᏤᎵ ᎧᏃᎮᏛ ᎪᏪᎵ ᏗᎯᏬᏂᎯᏍᏗ ᎢᎬᏁᏗ, Chat ᏗᎦᏙᏗ ᎦᎵᏦᏕ ᎤᎾᏄᎪᏫᏍᏗ. .zip WeKan ᎤᏄᎪᏫᏒᎯ Rocket.Chat CSV ᏴᏫᏗᏓᏍᏗ ᎤᏍᏗ ᎾᏍᏉ ᎪᎵᏰᏗ.",
"import-board-instruction-evernote": "Evernote ᎠᏂ, ᏗᎪᏪᎶᏗ ᎠᎴ ᏌᏉ ᏗᎪᏪᎶᏗ ᎪᏪᎵ .enex ᎪᏪᎵ ᎾᏍᎩᏯ ᎯᏄᎪᏫᏒ ᎠᎴ ᎠᏂ ᏑᏰᏍᎦ, ᎠᎴ ᎾᏍᎩ ᏗᎪᏪᎵ ᎯᏯᏝᏅ. ᏂᎦᏛ ᏗᎪᏪᎶᏗ ᏌᏉ ᎪᏪᎵ ᎢᎬᏁᏗ ᎤᏤᎵ ᏗᎪᏪᎵ ᎢᏧᎳᎭ, ᏚᎸᏫᏍᏓᏁᎸ ᏗᎦᎵᏍᏙᏗ ᏗᎪᎵᏰᏗ ᏗᎠᏎᏊᎢ ᎾᏍᎩᏯ, ᎤᏤᎵ tags ᏗᎪᏪᎳᏅᎯ ᎾᏍᎩᏯ ᎠᎴ ᎤᏤᎵ ᎠᏅᏓᏗᏍᏗ ᎤᎵᏍᏆᏗ ᎾᏍᎩᏯ; ᏗᎪᏪᎶᏗ ᎾᏍᎩ ᎠᏅᏓᏗᏍᏗ ᎤᏍᏆᏛ Done ᎠᏂ ᎠᏂᎦᏘᏴ. ᏗᏟᎶᏍᏔᏅ ᎠᎴ ᏗᏓᏠᎯᏍᏗ ᏗᎪᏪᎵ ᎥᏝ ᏴᏫᏗᏓᏍᏗ.",
"tool-group-kanban": "Kanban ᎠᎴ ᏚᏁᏤᎸ ᏗᏙᏗ",
"tool-group-issues": "ᎤᏓᏑᏯ ᏗᏓᏛᏍᏗ ᎠᎴ ᏧᏓᎴᏅᏛ ᎠᏍᏆᏂᎪᏙᏗ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "لە Redmine، Issues ی پڕۆژەکە بکەرەوە، لە خوارەوەی لیستەکە Also available in: CSV هەڵبژێرە، ستوونەکان دیاری بکە (All columns، لەگەڵ Description) و هەناردە بکە، پاشان CSV بلکێنە. Redmine ناوی ستوونەکان بە زمانەکەی تۆ دادەنێت، بۆیە پێش هەناردەکردن لە My account زمانەکەت بکە بە ئینگلیزی. هەر دۆخێک دەبێتە لیست و کێشەکان دەبنە کارت، لەگەڵ تراکەر وەک پێناسە، بەرپرس، نووسەر، بەروارەکان، ئەرکی دایک و کێشە پەیوەندیدارەکان؛ پێشینەیی، پۆل، وەشانی ئامانج، کاتی خەمڵێنراو، % Done و خانە تایبەتەکان دەبنە خانەی تایبەت.",
"import-board-instruction-notion": "لە Notion، بنکەدراوەکە وەک پەڕەیەکی تەواو بکەرەوە، ••• و Export هەڵبژێرە، Markdown & CSV دیاری بکە، و ئەو فایلە .zip ـە هەڵبژێرە کە دای دەگرێت، یان یەک CSV ی بنکەدراوە لەناویدا، یان ئەو CSV ـە بلکێنە. ستوونێک بە ناوی Status دەبێتە لیستەکان (ئەگەر نەبێت، یەکەم ستوون کە وەک هەڵبژاردن دەردەکەوێت، و ڕاپۆرتی هاوردەکردن دەڵێت کامەیە)؛ ڕیزەکان دەبنە کارت لەگەڵ سەردێڕ، تاگەکان وەک پێناسە، کەسەکان وەک ئەندام، بەروارەکان، و دەقی پەڕەکە وەک وەسف؛ ستوونەکانی تر دەبنە خانەی تایبەت. پەیوەندییەکان، وێنەکان و هاوپێچەکان هاوردە ناکرێن.",
"import-board-instruction-plane": "لە Plane، Workspace Settings بکەرەوە، Exports هەڵبژێرە، پڕۆژەکان وەک JSON، CSV یان Excel هەناردە بکە و فایلی .zip دابگرە، پاشان ئەو فایلە هەڵبژێرە، یان یەک فایل لەناویدا، یان JSON یان CSV بلکێنە. دۆخەکان دەبنە لیست، پڕۆژەکان دەبنە ڕێڕەو، و کێشەکان دەبنە کارت لەگەڵ ناسێنەر، دایک، بەرپرسەکان، پێناسەکان، بەروارەکان، بەستەرەکان و لێدوانەکانیان؛ پێشینەیی، خەمڵاندن، خول و مۆدیوڵ دەبنە خانەی تایبەت. هەناردەی Plane وەسف یان هاوپێچی تێدا نییە، بۆیە هاوردە ناکرێن.",
"import-board-instruction-fizzy": "لە Fizzy، هەژمارەکە لە «Account settings» هەناردە بکە، یان کارتەکانی خۆت بە «Download my data»، و ئەو فایلە ‎.zip ـە هەڵبژێرە کە Fizzy بۆتی دەنێرێت، یان فایلی ‎.json ـی کارتێک. تەختەکان دەبنە ڕێڕەو و ستوونەکان دەبنە لیست، لەگەڵ «Maybe?» و «Not now» و «Done» وەک لە Fizzy؛ کارتەکان وەسف، پێناسەکان، بەرپرسەکان، هەنگاوەکان وەک لیستی پشکنین، لێدوانەکان و فایلەکانیان دەپارێزن.",
"import-board-instruction-mail": "فایلێکی ‎.mbox هەڵبژێرە، وەک ئەوەی Thunderbird، Apple Mail، mutt یان Gmail لە ڕێگەی Google Takeout پاشەکەوتی دەکەن، یان تەنها نامەیەکی ‎.eml، یان دەقەکەی بلکێنە. هەر گفتوگۆیەک دەبێتە یەک کارت لە لیستی Inbox، لەگەڵ نێرەر و وەرگران و بابەتەکەی، تا لە دیمەنی Email دەربکەوێت؛ وەڵامەکان دەبنە لێدوانەکانی. پێناسەکانی Gmail دەبنە پێناسە. هاوپێچەکان هاوردە ناکرێن.",
"import-board-instruction-ical": "فایلێکی ڕۆژژمێری ‎.ics هەڵبژێرە، وەک ئەوەی Google Calendar، Apple Calendar یان Reminders، Thunderbird، Nextcloud یان Outlook هەناردەی دەکەن، یان دەقەکەی بلکێنە. ئەرکەکان بەپێی دۆخیان دەچنە To Do، In Progress، Done یان Cancelled، و ڕووداوەکان دەچنە Events، لەگەڵ بەرواری دەستپێک و کۆتاییان، تا لە دیمەنەکانی Calendar و Gantt دەربکەون. پۆلەکان و ئەولەویەت دەبنە پێناسە. بڕگە دووبارەبووەکان یەک جار هاوردە دەکرێن.",
"import-board-instruction-googletakeout": "لە takeout.google.com، Tasks، Keep، Mail، Calendar و Google Chat هەڵبژێرە، هەناردەکە دروست بکە و فایلی ‎.zip دابەزێنە، پاشان لێرە هەڵیبژێرە. هەر بەرهەمێک دەبێتە ڕێڕەوێک: پۆست بۆ دیمەنی Email، لیستی ئەرکەکان و تێبینییەکان لەگەڵ لیستی پشکنینیان، ڕووداوەکانی ڕۆژژمێر و ئەرکەکان لەگەڵ بەروار، و شوێنەکانی چات کە نامەکانیان لێدوانن بۆ دیمەنی Chat. بەرهەمەکانی تر و هاوپێچەکان هاوردە ناکرێن.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "لە Telegram Desktop، Settings، Advanced، Export Telegram data بکەرەوە، شێوازی JSON هەڵبژێرە و هەناردە بکە، پاشان فایلی result.json هەڵبژێرە، یان دەقەکەی بلکێنە. هەر چاتێک دەبێتە کارتێک لە Direct messages، Groups یان Channels، و نامەکانی دەبنە لێدوانەکانی کارتەکە، تا دیمەنی Chat چاتەکە پیشان بدات. وێنە و فایلەکان هاوردە ناکرێن.",
"import-board-instruction-whatsapp": "لە WhatsApp، چاتەکە بکەرەوە، Export chat بەبێ میدیا هەڵبژێرە، و فایلی ‎.txt لێرە هەڵبژێرە، یان دەقەکەی بلکێنە. چاتەکە دەبێتە کارتێک کە نامەکانی لێدوانەکانین، بە نێرەر و کاتیان، تا دیمەنی Chat پیشانی بدات. میدیا و نامەکانی سیستەم هاوردە ناکرێن.",
"import-board-instruction-discord": "کەناڵێکی Discord بە DiscordChatExporter بە شێوازی JSON هەناردە بکە و فایلی ‎.json هەڵبژێرە، یان دەقەکەی بلکێنە. کەناڵەکە دەبێتە کارتێک لە پۆلەکەیدا، و نامەکانی دەبنە لێدوانەکانی کارتەکە، تا دیمەنی Chat کەناڵەکە پیشان بدات. ڕاژەکار دەبێتە ڕێڕەوەکە. هاوپێچەکان هاوردە ناکرێن.",
"import-board-instruction-rocketchat": "لە Rocket.Chat، داتاکانت وەک JSON لە «My Data» هەناردە بکە و ئەو فایلە ‎.zip ـە هەڵبژێرە کە بۆتی دەنێرێت، یان فایلی ‎.json ـی هەناردەکراوی ژوورێک. هەر ژوورێک دەبێتە کارتێک و نامەکانی دەبنە لێدوانەکانی کارتەکە، تا دیمەنی Chat ژوورەکە پیشان بدات. ئەو ‎.zip ـەش دەخوێندرێتەوە کە WeKan بۆ هاوردەکەری CSV ـی Rocket.Chat هەناردەی دەکات.",
"import-board-instruction-evernote": "لە Evernote، تێبینییەکان یان دەفتەرێک وەک فایلی ‎.enex هەناردە بکە و لێرە هەڵیبژێرە، یان دەقەکەی بلکێنە. هەر تێبینییەک دەبێتە کارتێک لەگەڵ دەقەکەی، چوارگۆشەکانی ئەرکەکانی وەک لیستی پشکنین، تاگەکانی وەک پێناسە و بیرخەرەوەکەی وەک بەرواری کۆتایی؛ ئەو تێبینیانەی بیرخەرەوەکەیان تەواو بووە دەچنە Done. وێنە و فایلە هاوپێچەکان هاوردە ناکرێن.",
"tool-group-kanban": "ئامرازەکانی کانبان و پرۆژە",
"tool-group-issues": "بەدواداچوونی کێشەکان و کۆنترۆڵی وەشان",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "在 Redmine 中,打开项目的 Issues,在列表底部选择 Also available in: CSV,选择列(All columns,包含 Description)并导出,然后粘贴 CSV。Redmine 使用你的语言命名列,因此请在导出前将 My account 中的语言设为英语。每个状态会成为列表,问题会成为卡片,并保留作为标签的跟踪类型、被指派人、作者、日期、父任务和相关问题;优先级、类别、目标版本、预计时间、% Done 和自定义字段会成为自定义字段。",
"import-board-instruction-notion": "在 Notion 中,将数据库作为完整页面打开,选择 ••• 和 Export,选择 Markdown & CSV,然后选择下载的 .zip 文件,或其中一个数据库的 CSV 文件,也可粘贴该 CSV。名为 Status 的列会成为列表(如果没有,则使用第一个看起来像选择字段的列,导入报告会说明选择了哪一列);每行会成为卡片,并保留标题、标签、作为成员的人员、日期以及作为描述的页面文本;其他列会成为自定义字段。不导入关系、图片和附件。",
"import-board-instruction-plane": "在 Plane 中,打开 Workspace Settings,选择 Exports,将项目导出为 JSON、CSV 或 Excel 并下载 .zip 文件,然后选择该文件或其中的一个文件,也可粘贴 JSON 或 CSV。状态会成为列表,项目会成为泳道,问题会成为卡片,并保留标识符、父项、被指派人、标签、日期、链接和评论;优先级、估算、周期和模块会成为自定义字段。Plane 的导出不含描述和附件,因此不会导入这些内容。",
"import-board-instruction-fizzy": "在 Fizzy 中,在“Account settings”中导出账户,或用“Download my data”导出你自己的卡片,然后选择 Fizzy 发给你的 .zip 文件,或某张卡片的 .json 文件。板成为泳道,列成为列表,“Maybe?”、“Not now”和“Done”与 Fizzy 中相同;卡片保留其描述、标签、受让人、作为清单的步骤、评论和文件。",
"import-board-instruction-mail": "选择一个 .mbox 文件(Thunderbird、Apple Mail、mutt 或通过 Google Takeout 导出的 Gmail 所保存的那种),或一封 .eml 邮件,或粘贴其文本。每个会话成为 Inbox 列表中的一张卡片,带有发件人、收件人和主题,因此会显示在 Email 视图中;回复成为它的评论。Gmail 标签成为标签。附件不会导入。",
"import-board-instruction-ical": "选择一个 .ics 日历文件(由 Google Calendar、Apple Calendar 或 Reminders、Thunderbird、Nextcloud 或 Outlook 导出),或粘贴其文本。任务按其状态进入 To Do、In Progress、Done 或 Cancelled,事件进入 Events,并带有开始日期和到期日期,因此会显示在 Calendar 和 Gantt 视图中。类别和优先级成为标签。重复的项目只导入一次。",
"import-board-instruction-googletakeout": "在 takeout.google.com 上选择 Tasks、Keep、Mail、Calendar 和 Google Chat,创建导出并下载 .zip 文件,然后在这里选择它。每个产品成为一个泳道:邮件用于 Email 视图,任务列表和笔记带有其清单,日历事件和任务带有日期,聊天空间的消息成为 Chat 视图的评论。其他产品和附件不会导入。",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "在 Telegram Desktop 中打开 Settings、Advanced、Export Telegram data,选择 JSON 格式并导出,然后选择 result.json 文件,或粘贴其文本。每个聊天成为 Direct messages、Groups 或 Channels 中的一张卡片,其消息成为卡片的评论,因此 Chat 视图会显示该聊天。照片和文件不会导入。",
"import-board-instruction-whatsapp": "在 WhatsApp 中打开聊天,选择不含媒体的 Export chat,然后在这里选择 .txt 文件,或粘贴其文本。该聊天成为一张卡片,其消息按发送者和时间成为它的评论,因此 Chat 视图会显示它。媒体和系统消息不会导入。",
"import-board-instruction-discord": "使用 DiscordChatExporter 以 JSON 格式导出一个 Discord 频道并选择 .json 文件,或粘贴其文本。该频道成为其类别中的一张卡片,其消息成为卡片的评论,因此 Chat 视图会显示该频道。服务器成为泳道。附件不会导入。",
"import-board-instruction-rocketchat": "在 Rocket.Chat 中,在“My Data”中将你的数据导出为 JSON,然后选择它发给你的 .zip 文件,或某个房间导出的 .json 文件。每个房间成为一张卡片,其消息成为卡片的评论,因此 Chat 视图会显示该房间。WeKan 为 Rocket.Chat 的 CSV 导入器导出的 .zip 也可以读取。",
"import-board-instruction-evernote": "在 Evernote 中将笔记或笔记本导出为 .enex 文件,然后在这里选择它,或粘贴其文本。每条笔记成为一张卡片,带有其文本、作为清单的待办复选框、作为标签的标记,以及作为到期日的提醒;提醒已完成的笔记进入 Done。图片和附加文件不会导入。",
"tool-group-kanban": "看板与项目工具",
"tool-group-issues": "问题跟踪与版本控制",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "In Redmine, aprite Issues di u prughjettu, sceglite Also available in: CSV in fondu à a lista, sceglite e culonne (All columns, cù Description) è espurtate, po incullate u CSV. Redmine dà à e culonne nomi in a vostra lingua, dunque mettite a vostra lingua à English in My account prima d'espurtà. Ogni statu diventa una lista è e richieste diventanu carte, cù u tracker cum'è etichetta, persona assignata, autore, date, compitu parente è richieste ligate; a priurità, categuria, versione prevista, tempu stimatu, % Done è i campi persunalizati diventanu campi persunalizati.",
"import-board-instruction-notion": "In Notion, aprite a basa di dati cum'è pagina sana, sceglite ••• è Export, sceglite Markdown & CSV, è sceglite u schedariu .zip scaricatu, o un CSV di basa di dati ch'ellu cuntene, o incullate stu CSV. Una culonna chjamata Status diventa e liste (s'ella manca, a prima culonna chì pare una selezzione hè aduprata, è u raportu d'impurtazione dice quale); e linee diventanu carte cù u so titulu, etichette, persone cum'è membri, date, è u testu di a pagina cum'è discrizzione; l'altre culonne diventanu campi persunalizati. E rilazioni, imagine è appicci ùn sò micca impurtati.",
"import-board-instruction-plane": "In Plane, aprite Workspace Settings, sceglite Exports, espurtate i prughjetti cum'è JSON, CSV o Excel è scaricate u schedariu .zip, po sceglite stu schedariu, o un schedariu ch'ellu cuntene, o incullate u JSON o CSV. I stati diventanu liste, i prughjetti diventanu curridori, è e richieste diventanu carte cù u so identificatore, parente, persone assignate, etichette, date, ligami è cummenti; a priurità, stima, ciculu è modulu diventanu campi persunalizati. L'espurtazione di Plane ùn cuntene nè discrizzioni nè appicci, dunque ùn sò micca impurtati.",
"import-board-instruction-fizzy": "In Fizzy, spurtate u contu in «Account settings», o e vostre carte cù «Download my data», è sceglite u schedariu .zip chì Fizzy vi manda, o u schedariu .json di una carta. E tavule diventanu corsie è e culonne diventanu liste, cù «Maybe?», «Not now» è «Done» cum'è in Fizzy; e carte tenenu a so descrizzione, etichette, assignati, passi cum'è lista di cuntrollu, cummenti è schedarii.",
"import-board-instruction-mail": "Sceglite un schedariu .mbox, cum'è u salvanu Thunderbird, Apple Mail, mutt o Gmail per mezu di Google Takeout, o un solu messaghju .eml, o incullate u so testu. Ogni cunversazione diventa una carta in a lista Inbox, cù u so mandatore, i so destinatarii è u so sughjettu, per ch'ella si veda in a vista Email; e risposte diventanu i so cummenti. E etichette di Gmail diventanu etichette. L'aghjunti ùn sò micca impurtati.",
"import-board-instruction-ical": "Sceglite un schedariu di calendariu .ics, cum'è u spurtanu Google Calendar, Apple Calendar o Reminders, Thunderbird, Nextcloud o Outlook, o incullate u so testu. I compiti vanu in To Do, In Progress, Done o Cancelled secondu u so statu, è l'avvenimenti in Events, cù e so date di principiu è di scadenza, per ch'elli si vedinu in e viste Calendar è Gantt. E categurie è a priorità diventanu etichette. L'elementi chì si ripetenu sò impurtati una volta.",
"import-board-instruction-googletakeout": "Nant'à takeout.google.com, sceglite Tasks, Keep, Mail, Calendar è Google Chat, create l'esportazione è scaricate u schedariu .zip, po sceglitelu quì. Ogni pruduttu diventa una corsia: a posta per a vista Email, e liste di compiti è e note cù e so liste di cuntrollu, l'avvenimenti di calendariu è i compiti cù e date, è i spazii di chat chì i so messaghji sò cummenti per a vista Chat. L'altri prudutti è l'aghjunti ùn sò micca impurtati.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "In Telegram Desktop, aprite Settings, Advanced, Export Telegram data, sceglite u furmatu JSON è spurtate, po sceglite u schedariu result.json, o incullate u so testu. Ogni chat diventa una carta in Direct messages, Groups o Channels, è i so messaghji diventanu i cummenti di a carta, per chì a vista Chat mostri a chat. E foto è i schedarii ùn sò micca impurtati.",
"import-board-instruction-whatsapp": "In WhatsApp, aprite a chat, sceglite Export chat senza media, è sceglite quì u schedariu .txt, o incullate u so testu. A chat diventa una carta chì i so messaghji sò i so cummenti, da u so mandatore è l'ora, per chì a vista Chat a mostri. I media è i messaghji di u sistema ùn sò micca impurtati.",
"import-board-instruction-discord": "Spurtate un canale Discord cù DiscordChatExporter in u furmatu JSON è sceglite u schedariu .json, o incullate u so testu. U canale diventa una carta in a so categuria, è i so messaghji diventanu i cummenti di a carta, per chì a vista Chat mostri u canale. U servitore diventa a corsia. L'aghjunti ùn sò micca impurtati.",
"import-board-instruction-rocketchat": "In Rocket.Chat, spurtate i vostri dati in JSON in «My Data» è sceglite u schedariu .zip chì vi manda, o u schedariu .json spurtatu di una stanza. Ogni stanza diventa una carta è i so messaghji diventanu i cummenti di a carta, per chì a vista Chat mostri a stanza. Hè lettu ancu u .zip chì WeKan spurta per l'impurtadore CSV di Rocket.Chat.",
"import-board-instruction-evernote": "In Evernote, spurtate e note o un quaternu cum'è schedariu .enex è sceglitelu quì, o incullate u so testu. Ogni nota diventa una carta cù u so testu, e so caselle di compiti cum'è lista di cuntrollu, e so tag cum'è etichette è u so ramentu cum'è data di scadenza; e note chì u so ramentu hè fattu vanu in Done. L'imagine è i schedarii aghjunti ùn sò micca impurtati.",
"tool-group-kanban": "Strumenti Kanban è di prughjetti",
"tool-group-issues": "Seguitu di i prublemi è cuntrollu di versione",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "V Redmine otevřete Issues projektu, dole v seznamu zvolte Also available in: CSV, vyberte sloupce (All columns včetně Description) a exportujte. Poté CSV vložte. Redmine pojmenovává sloupce ve vašem jazyce, proto před exportem nastavte jazyk na English v My account. Každý stav se převede na seznam a požadavky na karty s typem požadavku jako štítkem, přiřazenou osobou, autorem, daty, nadřazeným úkolem a souvisejícími požadavky; priorita, kategorie, cílová verze, odhadovaný čas, % Done a vlastní pole se převedou na vlastní pole.",
"import-board-instruction-notion": "V Notion otevřete databázi jako celou stránku, zvolte ••• a Export, vyberte Markdown & CSV a poté stažený soubor .zip nebo jeden databázový CSV z jeho obsahu, případně tento CSV vložte. Sloupec nazvaný Status určuje seznamy (pokud chybí, použije se první sloupec připomínající výběrové pole a zpráva o importu uvede který). Řádky se převedou na karty s názvem, tagy jako štítky, osobami jako členy, daty a textem stránky jako popisem; ostatní sloupce se převedou na vlastní pole. Relace, obrázky a přílohy se neimportují.",
"import-board-instruction-plane": "V Plane otevřete Workspace Settings, zvolte Exports, exportujte projekty jako JSON, CSV nebo Excel a stáhněte soubor .zip. Poté vyberte tento soubor nebo jeden soubor z jeho obsahu, případně vložte JSON nebo CSV. Stavy se převedou na seznamy, projekty na dráhy a požadavky na karty s identifikátorem, nadřazeným požadavkem, přiřazenými osobami, štítky, daty, odkazy a komentáři; priorita, odhad, cyklus a modul se převedou na vlastní pole. Export z Plane neobsahuje popisy ani přílohy, takže se neimportují.",
"import-board-instruction-fizzy": "V aplikaci Fizzy exportujte účet v „Account settings“, nebo své vlastní karty pomocí „Download my data“, a vyberte soubor .zip, který vám Fizzy pošle, nebo soubor .json jedné karty. Tabla se stanou dráhami a sloupce zůstanou sloupci, s „Maybe?“, „Not now“ a „Done“ jako v aplikaci Fizzy; karty si ponechají popis, štítky, řešitele, kroky jako checklist, komentáře a soubory.",
"import-board-instruction-mail": "Vyberte soubor .mbox, jak jej ukládá Thunderbird, Apple Mail, mutt nebo Gmail přes Google Takeout, nebo jednu zprávu .eml, nebo vložte její text. Každá konverzace se stane jednou kartou ve sloupci Inbox, s odesílatelem, příjemci a předmětem, takže se zobrazí v zobrazení Email; odpovědi se stanou jejími komentáři. Štítky Gmailu se stanou štítky. Přílohy se neimportují.",
"import-board-instruction-ical": "Vyberte kalendářový soubor .ics, jak jej exportuje Google Calendar, Apple Calendar nebo Reminders, Thunderbird, Nextcloud nebo Outlook, nebo vložte jeho text. Úkoly jdou do To Do, In Progress, Done nebo Cancelled podle svého stavu a události do Events, s datem začátku a termínem, takže se zobrazí v zobrazeních Calendar a Gantt. Kategorie a priorita se stanou štítky. Opakující se položky se importují jednou.",
"import-board-instruction-googletakeout": "Na takeout.google.com vyberte Tasks, Keep, Mail, Calendar a Google Chat, vytvořte export a stáhněte soubor .zip, pak jej vyberte zde. Každý produkt se stane dráhou: pošta pro zobrazení Email, seznamy úkolů a poznámky s jejich checklisty, události kalendáře a úkoly s daty a chatovací prostory, jejichž zprávy jsou komentáři pro zobrazení Chat. Ostatní produkty a přílohy se neimportují.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "V Telegram Desktop otevřete Settings, Advanced, Export Telegram data, vyberte formát JSON a exportujte, pak vyberte soubor result.json, nebo vložte jeho text. Každý chat se stane kartou v Direct messages, Groups nebo Channels a jeho zprávy se stanou komentáři karty, takže zobrazení Chat ukáže chat. Fotografie a soubory se neimportují.",
"import-board-instruction-whatsapp": "Ve WhatsAppu otevřete chat, vyberte Export chat bez médií a vyberte zde soubor .txt, nebo vložte jeho text. Chat se stane kartou, jejíž zprávy jsou jejími komentáři podle odesílatele a času, takže jej zobrazení Chat ukáže. Média a systémové zprávy se neimportují.",
"import-board-instruction-discord": "Exportujte kanál Discordu pomocí DiscordChatExporter ve formátu JSON a vyberte soubor .json, nebo vložte jeho text. Kanál se stane kartou ve své kategorii a jeho zprávy se stanou komentáři karty, takže zobrazení Chat ukáže kanál. Server se stane dráhou. Přílohy se neimportují.",
"import-board-instruction-rocketchat": "V aplikaci Rocket.Chat exportujte svá data jako JSON v „My Data“ a vyberte soubor .zip, který vám pošle, nebo exportovaný soubor .json jedné místnosti. Každá místnost se stane kartou a její zprávy se stanou komentáři karty, takže zobrazení Chat ukáže místnost. Načte se i soubor .zip, který WeKan exportuje pro CSV importér aplikace Rocket.Chat.",
"import-board-instruction-evernote": "V Evernote exportujte poznámky nebo zápisník jako soubor .enex a vyberte jej zde, nebo vložte jeho text. Každá poznámka se stane kartou se svým textem, zaškrtávacími políčky úkolů jako checklistem, štítky jako štítky a připomínkou jako termínem; poznámky s dokončenou připomínkou jdou do Done. Obrázky a přiložené soubory se neimportují.",
"tool-group-kanban": "Kanban a nástroje pro projekty",
"tool-group-issues": "Sledování problémů a správa verzí",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "V Redmine otevřete Issues projektu, dole v seznamu zvolte Also available in: CSV, vyberte sloupce (All columns včetně Description) a exportujte. Poté CSV vložte. Redmine pojmenovává sloupce ve vašem jazyce, proto před exportem nastavte jazyk na English v My account. Každý stav se převede na seznam a požadavky na karty s typem požadavku jako štítkem, přiřazenou osobou, autorem, daty, nadřazeným úkolem a souvisejícími požadavky; priorita, kategorie, cílová verze, odhadovaný čas, % Done a vlastní pole se převedou na vlastní pole.",
"import-board-instruction-notion": "V Notion otevřete databázi jako celou stránku, zvolte ••• a Export, vyberte Markdown & CSV a poté stažený soubor .zip nebo jeden databázový CSV z jeho obsahu, případně tento CSV vložte. Sloupec nazvaný Status určuje seznamy (pokud chybí, použije se první sloupec připomínající výběrové pole a zpráva o importu uvede který). Řádky se převedou na karty s názvem, tagy jako štítky, osobami jako členy, daty a textem stránky jako popisem; ostatní sloupce se převedou na vlastní pole. Relace, obrázky a přílohy se neimportují.",
"import-board-instruction-plane": "V Plane otevřete Workspace Settings, zvolte Exports, exportujte projekty jako JSON, CSV nebo Excel a stáhněte soubor .zip. Poté vyberte tento soubor nebo jeden soubor z jeho obsahu, případně vložte JSON nebo CSV. Stavy se převedou na seznamy, projekty na dráhy a požadavky na karty s identifikátorem, nadřazeným požadavkem, přiřazenými osobami, štítky, daty, odkazy a komentáři; priorita, odhad, cyklus a modul se převedou na vlastní pole. Export z Plane neobsahuje popisy ani přílohy, takže se neimportují.",
"import-board-instruction-fizzy": "V aplikaci Fizzy exportujte účet v „Account settings“, nebo své vlastní karty pomocí „Download my data“, a vyberte soubor .zip, který vám Fizzy pošle, nebo soubor .json jedné karty. Tabla se stanou dráhami a sloupce zůstanou sloupci, s „Maybe?“, „Not now“ a „Done“ jako v aplikaci Fizzy; karty si ponechají popis, štítky, řešitele, kroky jako checklist, komentáře a soubory.",
"import-board-instruction-mail": "Vyberte soubor .mbox, jak jej ukládá Thunderbird, Apple Mail, mutt nebo Gmail přes Google Takeout, nebo jednu zprávu .eml, nebo vložte její text. Každá konverzace se stane jednou kartou ve sloupci Inbox, s odesílatelem, příjemci a předmětem, takže se zobrazí v zobrazení Email; odpovědi se stanou jejími komentáři. Štítky Gmailu se stanou štítky. Přílohy se neimportují.",
"import-board-instruction-ical": "Vyberte kalendářový soubor .ics, jak jej exportuje Google Calendar, Apple Calendar nebo Reminders, Thunderbird, Nextcloud nebo Outlook, nebo vložte jeho text. Úkoly jdou do To Do, In Progress, Done nebo Cancelled podle svého stavu a události do Events, s datem začátku a termínem, takže se zobrazí v zobrazeních Calendar a Gantt. Kategorie a priorita se stanou štítky. Opakující se položky se importují jednou.",
"import-board-instruction-googletakeout": "Na takeout.google.com vyberte Tasks, Keep, Mail, Calendar a Google Chat, vytvořte export a stáhněte soubor .zip, pak jej vyberte zde. Každý produkt se stane dráhou: pošta pro zobrazení Email, seznamy úkolů a poznámky s jejich checklisty, události kalendáře a úkoly s daty a chatovací prostory, jejichž zprávy jsou komentáři pro zobrazení Chat. Ostatní produkty a přílohy se neimportují.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "V Telegram Desktop otevřete Settings, Advanced, Export Telegram data, vyberte formát JSON a exportujte, pak vyberte soubor result.json, nebo vložte jeho text. Každý chat se stane kartou v Direct messages, Groups nebo Channels a jeho zprávy se stanou komentáři karty, takže zobrazení Chat ukáže chat. Fotografie a soubory se neimportují.",
"import-board-instruction-whatsapp": "Ve WhatsAppu otevřete chat, vyberte Export chat bez médií a vyberte zde soubor .txt, nebo vložte jeho text. Chat se stane kartou, jejíž zprávy jsou jejími komentáři podle odesílatele a času, takže jej zobrazení Chat ukáže. Média a systémové zprávy se neimportují.",
"import-board-instruction-discord": "Exportujte kanál Discordu pomocí DiscordChatExporter ve formátu JSON a vyberte soubor .json, nebo vložte jeho text. Kanál se stane kartou ve své kategorii a jeho zprávy se stanou komentáři karty, takže zobrazení Chat ukáže kanál. Server se stane dráhou. Přílohy se neimportují.",
"import-board-instruction-rocketchat": "V aplikaci Rocket.Chat exportujte svá data jako JSON v „My Data“ a vyberte soubor .zip, který vám pošle, nebo exportovaný soubor .json jedné místnosti. Každá místnost se stane kartou a její zprávy se stanou komentáři karty, takže zobrazení Chat ukáže místnost. Načte se i soubor .zip, který WeKan exportuje pro CSV importér aplikace Rocket.Chat.",
"import-board-instruction-evernote": "V Evernote exportujte poznámky nebo zápisník jako soubor .enex a vyberte jej zde, nebo vložte jeho text. Každá poznámka se stane kartou se svým textem, zaškrtávacími políčky úkolů jako checklistem, štítky jako štítky a připomínkou jako termínem; poznámky s dokončenou připomínkou jdou do Done. Obrázky a přiložené soubory se neimportují.",
"tool-group-kanban": "Kanban a nástroje pro projekty",
"tool-group-issues": "Sledování problémů a správa verzí",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "W Redmine òtemkni Issues projektu, wëbierzë Also available in: CSV na spòdkù lëstë, wëbierzë kòlumnë (All columns, z Description) i wëekspòrtëjë, pòtemù wklejë CSV. Redmine dôwô kòlumnóm miona w twòjim jãzëkù, tej przed ekspòrtã nastôwi anielsczi w My account. Kòżdi status stôwô sã lëstą, a zgłoszenia kôrtama, z trackerã jakno etikétą, òdpòwiedzalnym, ùsôdzcą, datumama, nadrzãdnym zadanim i sparłãczonyma zgłoszeniama; priorytet, kategòrëjô, docélowô wersjô, òcenioni czas, % Done i włôsné pòla stôwają sã włôsnyma pòlama.",
"import-board-instruction-notion": "W Notion òtemkni bazã pòdôwków jakno całą starnã, wëbierzë ••• i Export, wëbierzë Markdown & CSV i wëbierzë lopk .zip, chtëren sã scygnie, abò jeden CSV bazë z niegò, abò wklejë nen CSV. Kòlumna z mionã Status stôwô sã lëstama (bez ni robi to pierszô kòlumna, chtërna wëzdrzi jak wëbiér, a rapòrt impòrtu gôdô chtërna); rédżi stôwają sã kôrtama z jich titlã, tagama jakno etikétama, lëdzama jakno nôleżnikama, datumama i tekstã starnë jakno òpisënkã; jinszé kòlumnë stôwają sã włôsnyma pòlama. Relacje, òbrazë i załączniczi nie są impòrtowóné.",
"import-board-instruction-plane": "W Plane òtemkni Workspace Settings, wëbierzë Exports, wëekspòrtëjë projektë jakno JSON, CSV abò Excel i scygni lopk .zip, pòtemù wëbierzë nen lopk abò jeden lopk z jegò strzodka, abò wklejë JSON abò CSV. Stónë stôwają sã lëstama, projektë stegnama, a zgłoszenia kôrtama z jich identifikatorã, nadrzãdnym, òdpòwiedzalnyma, etikétama, datumama, lënkama i kòmentôrzama; priorytet, òcena, cykl i mòduł stôwają sã włôsnyma pòlama. Ekspòrt Plane ni mô òpisënków ani załączników, tej nie są impòrtowóné.",
"import-board-instruction-fizzy": "W Fizzy wëeksportëjë kònto w „Account settings“, abò swòje kôrtë z „Download my data“, ë wëbierzë lopk .zip, jaczi Fizzy ce sélô, abò lopk .json jedny kôrtë. Tôfle òstają stegnama, a kòlumnë òstają lëstama, z „Maybe?“, „Not now“ ë „Done“ jak w Fizzy; kôrtë zachòwiwają swój òpisënk, etikétë, òdpòwiedzalnëch, krokë jakno lëstã kòntrolë, kòmentôrze ë lopczi.",
"import-board-instruction-mail": "Wëbierzë lopk .mbox, jak gò zapisëją Thunderbird, Apple Mail, mutt abò Gmail przez Google Takeout, abò jedną wiadło .eml, abò wkleji jegò tekst. Kòżdô rozmòwa òstaje jedną kôrtą w lëstë Inbox, z jeji nadôwcą, òdbiérnikama ë tematą, bë bëła widzałô w widoku Email; òdpòwiedzë òstają jeji kòmentôrzama. Etikétë Gmaila òstają etikétama. Przëłączi nie są impòrtowóné.",
"import-board-instruction-ical": "Wëbierzë lopk kalãdôrza .ics, jak gò eksportëją Google Calendar, Apple Calendar abò Reminders, Thunderbird, Nextcloud abò Outlook, abò wkleji jegò tekst. Zadania jidą do To Do, In Progress, Done abò Cancelled wedle jich statusu, a wëdarzenia do Events, z jich datama zaczątku ë terminu, bë bëłë widzałé w widokach Calendar ë Gantt. Kategòrie ë priorytet òstają etikétama. Pòwtôrzającé sã elementë są impòrtowóné jeden rôz.",
"import-board-instruction-googletakeout": "Na takeout.google.com wëbierzë Tasks, Keep, Mail, Calendar ë Google Chat, ùsadzë eksport ë scygni lopk .zip, pòtemù wëbierzë gò tuwò. Kòżdi produkt òstaje stegną: pòczta dlô widoku Email, lëstë zadaniów ë notatczi z jich lëstama kòntrolë, wëdarzenia kalãdôrza ë zadania z datama, ë rëmë czatu, chtërnëch wiadła są kòmentôrzama dlô widoku Chat. Jinszé produktë ë przëłączi nie są impòrtowóné.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "W Telegram Desktop òtemkni Settings, Advanced, Export Telegram data, wëbierzë fòrmat JSON ë wëeksportëjë, pòtemù wëbierzë lopk result.json, abò wkleji jegò tekst. Kòżdi czat òstaje kôrtą w Direct messages, Groups abò Channels, a jegò wiadła òstają kòmentôrzama kôrtë, bë widok Chat pòkazywôł czat. Òdjimczi ë lopczi nie są impòrtowóné.",
"import-board-instruction-whatsapp": "W WhatsAppie òtemkni czat, wëbierzë Export chat bez mediów, ë wëbierzë tuwò lopk .txt, abò wkleji jegò tekst. Czat òstaje kôrtą, chtërny wiadła są jegò kòmentôrzama, wedle nadôwcë ë czasu, bë widok Chat gò pòkazywôł. Media ë systemòwé wiadła nie są impòrtowóné.",
"import-board-instruction-discord": "Wëeksportëjë kanal Discorda z DiscordChatExporter w fòrmace JSON ë wëbierzë lopk .json, abò wkleji jegò tekst. Kanal òstaje kôrtą w swòji kategòrii, a jegò wiadła òstają kòmentôrzama kôrtë, bë widok Chat pòkazywôł kanal. Serwer òstaje stegną. Przëłączi nie są impòrtowóné.",
"import-board-instruction-rocketchat": "W Rocket.Chat wëeksportëjë swòje dóné jakno JSON w „My Data“ ë wëbierzë lopk .zip, jaczi ce sélô, abò wëeksportowóny lopk .json jedny jizbë. Kòżdô jizba òstaje kôrtą, a ji wiadła òstają kòmentôrzama kôrtë, bë widok Chat pòkazywôł jizbã. Czëtóny je téż .zip, jaczi WeKan eksportëje dlô impòrtera CSV z Rocket.Chat.",
"import-board-instruction-evernote": "W Evernote wëeksportëjë notatczi abò notownik jakno lopk .enex ë wëbierzë gò tuwò, abò wkleji jegò tekst. Kòżdô notatka òstaje kôrtą z swòjim tekstã, swòjima pòlama zadaniów jakno lëstą kòntrolë, swòjima tagama jakno etikétama ë swòjim przëbôczenim jakno terminã; notatczi z zrobionym przëbôczenim jidą do Done. Òbrôzczi ë przëłączoné lopczi nie są impòrtowóné.",
"tool-group-kanban": "Nôrzãdza Kanban ë do projektów",
"tool-group-issues": "Śledzenié problemów ë kòntrola wersëji",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine-ра проектӑн Issues уҫӑр, списокӑн аялти пайӗнче Also available in: CSV суйлӑр, юпасене суйлӑр (All columns, Description-пе) тата экспортлӑр, унтан CSV лартӑр. Redmine юпасене сирӗн чӗлхепе ятлать, ҫавӑнпа экспортличчен My account-ра чӗлхене акӑлчанла лартӑр. Кашни тӑрӑм список, ыйтусем карточкӑсем пулаҫҫӗ, трекер паллӑ пулать, яваплӑ ҫынпа, авторпа, кунсемпе, ашшӗ ӗҫӗпе тата ҫыхӑннӑ ыйтусемпе; малтанлӑх, категори, тӗллев версийӗ, шутланӑ вӑхӑт, % Done тата уйрӑм хирсем уйрӑм хирсем пулаҫҫӗ.",
"import-board-instruction-notion": "Notion-ра даннӑйсен базине тулли страница пек уҫӑр, ••• тата Export суйлӑр, Markdown & CSV суйлӑр, унтан вӑл тиесе антарнӑ .zip файлне, е унти пӗр базӑн CSV-не суйлӑр, е ҫав CSV-не лартӑр. Status ятлӑ юпа спискӑсем пулать (вӑл ҫук пулсан — суйлав пек курӑнакан пӗрремӗш юпа, импорт отчечӗ хӑшне калать); йӗркесем карточкӑсем пулаҫҫӗ, вӗсен ячӗпе, паллӑсем пулнӑ тегӗсемпе, хутшӑнакансем пулнӑ ҫыннисемпе, кунӗсемпе, ӑнлантару пулнӑ страница текстӗпе; ытти юпасем уйрӑм хирсем пулаҫҫӗ. Ҫыхӑнусем, ӳкерчӗксем тата хушӑмсем импортланмаҫҫӗ.",
"import-board-instruction-plane": "Plane-ра Workspace Settings уҫӑр, Exports суйлӑр, проектсене JSON, CSV е Excel пек экспортлӑр тата .zip файлне тиесе антарӑр, унтан ҫав файла, е унӑн ӑшӗнчи пӗр файла суйлӑр, е JSON е CSV лартӑр. Тӑрӑмсем спискӑсем, проектсем ҫулсем, ыйтусем карточкӑсем пулаҫҫӗ, вӗсен идентификаторӗпе, ашшӗпе, яваплӑ ҫыннисемпе, паллисемпе, кунӗсемпе, ҫыххисемпе тата хушса каланисемпе; малтанлӑх, хаклав, цикл тата модуль уйрӑм хирсем пулаҫҫӗ. Plane экспортӗнче ӑнлантарусем те хушӑмсем те ҫук, ҫавӑнпа вӗсем импортланмаҫҫӗ.",
"import-board-instruction-fizzy": "Fizzy-ра аккаунта «Account settings» пайӗнче, е хӑвӑр карточкӑсене «Download my data» урлӑ экспортлӑр тата Fizzy сире янӑ .zip файлне, е пӗр карточкӑн .json файлне суйлӑр. Хӑмасем ҫулсем пулаҫҫӗ, юпасем спискӑсем пулаҫҫӗ, «Maybe?», «Not now» тата «Done» Fizzy-ри пекех; карточкӑсем хӑйсен ӑнлантарӑвне, паллисене, яваплисене, утӑмсене тӗрӗслев списки пек, хушса каланисене тата файлсене упраҫҫӗ.",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt е Google Takeout урлӑ Gmail упракан .mbox файла, е пӗр .eml ҫырӑва суйлӑр, е унӑн текстне лартӑр. Кашни калаҫу хӑйӗн яракан, илекенӗсемпе темипе Inbox спискинче пӗр карточкӑ пулса тӑрать, ҫавӑнпа Email курӑнӑвӗнче курӑнать; хуравсем унӑн хушса каланисем пулаҫҫӗ. Gmail паллисем паллӑсем пулаҫҫӗ. Хушӑмсем импортланмаҫҫӗ.",
"import-board-instruction-ical": "Google Calendar, Apple Calendar е Reminders, Thunderbird, Nextcloud е Outlook экспортлакан .ics календарь файлне суйлӑр, е унӑн текстне лартӑр. Ӗҫсем хӑйсен тӑрӑмӗ тӑрӑх To Do, In Progress, Done е Cancelled ҫине, пулӑмсем Events ҫине пуҫламӑш тата вӗҫленӳ кунӗсемпе каяҫҫӗ, ҫавӑнпа Calendar тата Gantt курӑнӑвӗсенче курӑнаҫҫӗ. Категорисем тата малтанлӑх паллӑсем пулаҫҫӗ. Тепӗр хут пулакан элементсем пӗрре импортланаҫҫӗ.",
"import-board-instruction-googletakeout": "takeout.google.com ҫинче Tasks, Keep, Mail, Calendar тата Google Chat суйлӑр, экспорт тӑвӑр тата .zip файла илӗр, унтан ӑна кунта суйлӑр. Кашни продукт ҫул пулса тӑрать: Email курӑнӑвӗ валли почта, тӗрӗслев спискисемпе ӗҫ спискисем тата асӑрхавсем, кунсемпе календарь пулӑмӗсем тата ӗҫсем, тата ҫырӑвӗсем Chat курӑнӑвӗ валли хушса калани пулакан чат вырӑнӗсем. Ытти продуктсем тата хушӑмсем импортланмаҫҫӗ.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop-ра Settings, Advanced, Export Telegram data уҫӑр, JSON форматне суйласа экспортлӑр, унтан result.json файлне суйлӑр, е унӑн текстне лартӑр. Кашни чат Direct messages, Groups е Channels ӑшӗнче карточкӑ пулса тӑрать, унӑн ҫырӑвӗсем карточкӑн хушса каланисем пулаҫҫӗ, ҫавӑнпа Chat курӑнӑвӗ чата кӑтартать. Сӑнӳкерчӗксем тата файлсем импортланмаҫҫӗ.",
"import-board-instruction-whatsapp": "WhatsApp-ра чата уҫӑр, медиасӑр Export chat суйлӑр, тата .txt файлне кунта суйлӑр, е унӑн текстне лартӑр. Чат ҫырӑвӗсем яракан тата вӑхӑт тӑрӑх унӑн хушса каланисем пулакан карточкӑ пулса тӑрать, ҫавӑнпа Chat курӑнӑвӗ ӑна кӑтартать. Медиа тата тытӑм ҫырӑвӗсем импортланмаҫҫӗ.",
"import-board-instruction-discord": "Discord каналне DiscordChatExporter урлӑ JSON форматпа экспортлӑр тата .json файлне суйлӑр, е унӑн текстне лартӑр. Канал хӑйӗн категорийӗнче карточкӑ пулса тӑрать, унӑн ҫырӑвӗсем карточкӑн хушса каланисем пулаҫҫӗ, ҫавӑнпа Chat курӑнӑвӗ канала кӑтартать. Сервер ҫул пулса тӑрать. Хушӑмсем импортланмаҫҫӗ.",
"import-board-instruction-rocketchat": "Rocket.Chat-ра хӑвӑр даннӑйӑрсене «My Data» пайӗнче JSON пек экспортлӑр тата вӑл сире янӑ .zip файлне, е пӗр пӳлӗмӗн экспортланӑ .json файлне суйлӑр. Кашни пӳлӗм карточкӑ пулса тӑрать, унӑн ҫырӑвӗсем карточкӑн хушса каланисем пулаҫҫӗ, ҫавӑнпа Chat курӑнӑвӗ пӳлӗме кӑтартать. WeKan Rocket.Chat-ӑн CSV импортерӗ валли экспортланӑ .zip та вуланать.",
"import-board-instruction-evernote": "Evernote-ра асӑрхавсене е асӑрхав кӗнекине .enex файл пек экспортлӑр тата ӑна кунта суйлӑр, е унӑн текстне лартӑр. Кашни асӑрхав хӑйӗн текстӗпе, тӗрӗслев списокӗ пек ӗҫ паллисемпе, паллӑсем пек тегӗсемпе тата вӗҫленӳ кунӗ пек аса илтерӗвӗпе карточкӑ пулса тӑрать; аса илтерӗвӗ пурнӑҫланнӑ асӑрхавсем Done ҫине каяҫҫӗ. Ӳкерчӗксем тата хушнӑ файлсем импортланмаҫҫӗ.",
"tool-group-kanban": "Канбан тата проект хатӗрӗсем",
"tool-group-issues": "Йӑнӑшсене йӗрлени тата версисен тытӑмӗ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Yn Redmine, agorwch Issues y prosiect, dewiswch Also available in: CSV ar waelod y rhestr, dewiswch y colofnau (All columns, gyda Description) ac allforiwch, yna gludwch y CSV. Mae Redmine yn enwi'r colofnau yn eich iaith chi, felly gosodwch eich iaith i Saesneg yn My account cyn allforio. Daw pob statws yn rhestr a materion yn gardiau, gyda'r tracker fel label, aseinai, awdur, dyddiadau, tasg rhiant a materion cysylltiedig; daw blaenoriaeth, categori, fersiwn targed, amser amcangyfrifedig, % Done a meysydd personol yn feysydd personol.",
"import-board-instruction-notion": "Yn Notion, agorwch y gronfa ddata fel tudalen lawn, dewiswch ••• ac Export, dewiswch Markdown & CSV, a dewiswch y ffeil .zip y mae'n ei lawrlwytho, neu un CSV cronfa ddata ohoni, neu gludwch y CSV hwnnw. Daw colofn o'r enw Status yn rhestrau (hebddi, y golofn gyntaf sy'n edrych fel dewis, ac mae'r adroddiad mewnforio yn dweud pa un); daw rhesi yn gardiau gyda'u teitl, tagiau fel labeli, pobl fel aelodau, dyddiadau, a thestun y dudalen fel disgrifiad; daw colofnau eraill yn feysydd personol. Ni chaiff perthnasoedd, delweddau ac ymlyniadau eu mewnforio.",
"import-board-instruction-plane": "Yn Plane, agorwch Workspace Settings, dewiswch Exports, allforiwch y prosiectau fel JSON, CSV neu Excel a lawrlwythwch y ffeil .zip, yna dewiswch y ffeil honno, neu un ffeil o'i mewn, neu gludwch y JSON neu'r CSV. Daw cyflyrau yn rhestrau, prosiectau yn lonydd nofio, a materion yn gardiau gyda'u dynodwr, rhiant, aseineion, labeli, dyddiadau, dolenni a sylwadau; daw blaenoriaeth, amcangyfrif, cylch a modiwl yn feysydd personol. Nid oes disgrifiadau nac ymlyniadau yn allforio Plane, felly ni chânt eu mewnforio.",
"import-board-instruction-fizzy": "Yn Fizzy, allforiwch y cyfrif yn \"Account settings\", neu eich cardiau eich hun gyda \"Download my data\", a dewiswch y ffeil .zip y mae Fizzy yn ei hanfon atoch, neu ffeil .json un cerdyn. Mae byrddau'n dod yn lonydd nofio a cholofnau'n dod yn rhestrau, gyda \"Maybe?\", \"Not now\" a \"Done\" fel yn Fizzy; mae cardiau'n cadw eu disgrifiad, labeli, aseineion, camau fel rhestr wirio, sylwadau a ffeiliau.",
"import-board-instruction-mail": "Dewiswch ffeil .mbox, fel y mae Thunderbird, Apple Mail, mutt neu Gmail drwy Google Takeout yn ei chadw, neu un neges .eml, neu gludwch ei thestun. Mae pob sgwrs yn dod yn un cerdyn yn y rhestr Inbox, gyda'i hanfonwr, ei derbynwyr a'i phwnc, fel ei bod yn ymddangos yn y wedd Email; mae'r atebion yn dod yn sylwadau iddi. Mae labeli Gmail yn dod yn labeli. Nid yw atodiadau'n cael eu mewnforio.",
"import-board-instruction-ical": "Dewiswch ffeil calendr .ics, fel y mae Google Calendar, Apple Calendar neu Reminders, Thunderbird, Nextcloud neu Outlook yn ei hallforio, neu gludwch ei thestun. Mae tasgau'n mynd i To Do, In Progress, Done neu Cancelled yn ôl eu statws, a digwyddiadau i Events, gyda'u dyddiadau cychwyn a dyledus, fel eu bod yn ymddangos yn y gweddau Calendar a Gantt. Mae categorïau a blaenoriaeth yn dod yn labeli. Mae eitemau sy'n ailadrodd yn cael eu mewnforio unwaith.",
"import-board-instruction-googletakeout": "Yn takeout.google.com, dewiswch Tasks, Keep, Mail, Calendar a Google Chat, crëwch yr allforyn a lawrlwythwch y ffeil .zip, yna dewiswch hi yma. Mae pob cynnyrch yn dod yn lôn nofio: post ar gyfer y wedd Email, rhestrau tasgau a nodiadau gyda'u rhestrau gwirio, digwyddiadau calendr a thasgau gyda dyddiadau, a gofodau sgwrsio y mae eu negeseuon yn sylwadau ar gyfer y wedd Chat. Nid yw cynhyrchion eraill ac atodiadau'n cael eu mewnforio.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Yn Telegram Desktop, agorwch Settings, Advanced, Export Telegram data, dewiswch y fformat JSON ac allforiwch, yna dewiswch y ffeil result.json, neu gludwch ei thestun. Mae pob sgwrs yn dod yn gerdyn yn Direct messages, Groups neu Channels, ac mae ei negeseuon yn dod yn sylwadau'r cerdyn, fel bod y wedd Chat yn dangos y sgwrs. Nid yw lluniau a ffeiliau'n cael eu mewnforio.",
"import-board-instruction-whatsapp": "Yn WhatsApp, agorwch y sgwrs, dewiswch Export chat heb gyfryngau, a dewiswch y ffeil .txt yma, neu gludwch ei thestun. Mae'r sgwrs yn dod yn gerdyn y mae ei negeseuon yn sylwadau iddo, yn ôl eu hanfonwr a'u hamser, fel bod y wedd Chat yn ei dangos. Nid yw cyfryngau a negeseuon system yn cael eu mewnforio.",
"import-board-instruction-discord": "Allforiwch sianel Discord gyda DiscordChatExporter yn y fformat JSON a dewiswch y ffeil .json, neu gludwch ei thestun. Mae'r sianel yn dod yn gerdyn yn ei chategori, ac mae ei negeseuon yn dod yn sylwadau'r cerdyn, fel bod y wedd Chat yn dangos y sianel. Mae'r gweinydd yn dod yn lôn nofio. Nid yw atodiadau'n cael eu mewnforio.",
"import-board-instruction-rocketchat": "Yn Rocket.Chat, allforiwch eich data fel JSON yn \"My Data\" a dewiswch y ffeil .zip y mae'n ei hanfon atoch, neu ffeil .json wedi'i hallforio o un ystafell. Mae pob ystafell yn dod yn gerdyn a'i negeseuon yn dod yn sylwadau'r cerdyn, fel bod y wedd Chat yn dangos yr ystafell. Mae'r .zip y mae WeKan yn ei allforio ar gyfer mewnforiwr CSV Rocket.Chat yn cael ei ddarllen hefyd.",
"import-board-instruction-evernote": "Yn Evernote, allforiwch y nodiadau neu lyfr nodiadau fel ffeil .enex a dewiswch hi yma, neu gludwch ei thestun. Mae pob nodyn yn dod yn gerdyn gyda'i destun, ei flychau ticio tasgau fel rhestr wirio, ei dagiau fel labeli a'i nodyn atgoffa fel y dyddiad dyledus; mae nodiadau y mae eu nodyn atgoffa wedi'i wneud yn mynd i Done. Nid yw delweddau a ffeiliau atodedig yn cael eu mewnforio.",
"tool-group-kanban": "Offer Kanban a phrosiectau",
"tool-group-issues": "Tracwyr problemau a rheoli fersiynau",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Yn Redmine, agorwch Issues y prosiect, dewiswch Also available in: CSV ar waelod y rhestr, dewiswch y colofnau (All columns, gyda Description) ac allforiwch, yna gludwch y CSV. Mae Redmine yn enwi'r colofnau yn eich iaith chi, felly gosodwch eich iaith i Saesneg yn My account cyn allforio. Daw pob statws yn rhestr a materion yn gardiau, gyda'r tracker fel label, aseinai, awdur, dyddiadau, tasg rhiant a materion cysylltiedig; daw blaenoriaeth, categori, fersiwn targed, amser amcangyfrifedig, % Done a meysydd personol yn feysydd personol.",
"import-board-instruction-notion": "Yn Notion, agorwch y gronfa ddata fel tudalen lawn, dewiswch ••• ac Export, dewiswch Markdown & CSV, a dewiswch y ffeil .zip y mae'n ei lawrlwytho, neu un CSV cronfa ddata ohoni, neu gludwch y CSV hwnnw. Daw colofn o'r enw Status yn rhestrau (hebddi, y golofn gyntaf sy'n edrych fel dewis sy'n gwneud hynny, ac mae'r adroddiad mewnforio yn dweud pa un); daw rhesi yn gardiau gyda'u teitl, tagiau fel labeli, pobl fel aelodau, dyddiadau, a thestun y dudalen fel disgrifiad; daw colofnau eraill yn feysydd personol. Nid yw perthnasoedd, delweddau ac ymlyniadau'n cael eu mewnforio.",
"import-board-instruction-plane": "Yn Plane, agorwch Workspace Settings, dewiswch Exports, allforiwch y prosiectau fel JSON, CSV neu Excel a lawrlwythwch y ffeil .zip, yna dewiswch y ffeil honno, neu un ffeil o'i mewn, neu gludwch y JSON neu'r CSV. Daw cyflyrau yn rhestrau, prosiectau yn lonydd nofio, a materion yn gardiau gyda'u dynodwr, rhiant, aseineion, labeli, dyddiadau, dolenni a sylwadau; daw blaenoriaeth, amcangyfrif, cylch a modiwl yn feysydd personol. Nid oes disgrifiadau nac ymlyniadau yn allforio Plane, felly nid ydynt yn cael eu mewnforio.",
"import-board-instruction-fizzy": "Yn Fizzy, allforiwch y cyfrif yn \"Account settings\", neu eich cardiau eich hun gyda \"Download my data\", a dewiswch y ffeil .zip y mae Fizzy yn ei hanfon atoch, neu ffeil .json un cerdyn. Mae byrddau'n dod yn lonydd nofio a cholofnau'n dod yn rhestrau, gyda \"Maybe?\", \"Not now\" a \"Done\" fel yn Fizzy; mae cardiau'n cadw eu disgrifiad, labeli, aseineion, camau fel rhestr wirio, sylwadau a ffeiliau.",
"import-board-instruction-mail": "Dewiswch ffeil .mbox, fel y mae Thunderbird, Apple Mail, mutt neu Gmail drwy Google Takeout yn ei chadw, neu un neges .eml, neu gludwch ei thestun. Mae pob sgwrs yn dod yn un cerdyn yn y rhestr Inbox, gyda'i hanfonwr, ei derbynwyr a'i phwnc, fel ei bod yn ymddangos yn y wedd Email; mae'r atebion yn dod yn sylwadau iddi. Mae labeli Gmail yn dod yn labeli. Nid yw atodiadau'n cael eu mewnforio.",
"import-board-instruction-ical": "Dewiswch ffeil calendr .ics, fel y mae Google Calendar, Apple Calendar neu Reminders, Thunderbird, Nextcloud neu Outlook yn ei hallforio, neu gludwch ei thestun. Mae tasgau'n mynd i To Do, In Progress, Done neu Cancelled yn ôl eu statws, a digwyddiadau i Events, gyda'u dyddiadau dechrau a chwblhau, fel eu bod yn ymddangos yn y gweddau Calendar a Gantt. Mae categorïau a blaenoriaeth yn dod yn labeli. Mae eitemau sy'n ailadrodd yn cael eu mewnforio unwaith.",
"import-board-instruction-googletakeout": "Yn takeout.google.com, dewiswch Tasks, Keep, Mail, Calendar a Google Chat, crëwch yr allforiad a lawrlwythwch y ffeil .zip, yna dewiswch hi yma. Mae pob cynnyrch yn dod yn lôn nofio: post ar gyfer y wedd Email, rhestrau tasgau a nodiadau gyda'u rhestrau gwirio, digwyddiadau calendr a thasgau gyda dyddiadau, a gofodau sgwrsio y mae eu negeseuon yn sylwadau ar gyfer y wedd Chat. Nid yw cynhyrchion eraill ac atodiadau'n cael eu mewnforio.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Yn Telegram Desktop, agorwch Settings, Advanced, Export Telegram data, dewiswch y fformat JSON ac allforiwch, yna dewiswch y ffeil result.json, neu gludwch ei thestun. Mae pob sgwrs yn dod yn gerdyn yn Direct messages, Groups neu Channels, ac mae ei negeseuon yn dod yn sylwadau'r cerdyn, fel bod y wedd Chat yn dangos y sgwrs. Nid yw lluniau a ffeiliau'n cael eu mewnforio.",
"import-board-instruction-whatsapp": "Yn WhatsApp, agorwch y sgwrs, dewiswch Export chat heb gyfryngau, a dewiswch y ffeil .txt yma, neu gludwch ei thestun. Mae'r sgwrs yn dod yn gerdyn y mae ei negeseuon yn sylwadau iddo, yn ôl eu hanfonwr a'u hamser, fel bod y wedd Chat yn ei dangos. Nid yw cyfryngau a negeseuon system yn cael eu mewnforio.",
"import-board-instruction-discord": "Allforiwch sianel Discord gyda DiscordChatExporter yn y fformat JSON a dewiswch y ffeil .json, neu gludwch ei thestun. Mae'r sianel yn dod yn gerdyn yn ei chategori, ac mae ei negeseuon yn dod yn sylwadau'r cerdyn, fel bod y wedd Chat yn dangos y sianel. Mae'r gweinydd yn dod yn lôn nofio. Nid yw atodiadau'n cael eu mewnforio.",
"import-board-instruction-rocketchat": "Yn Rocket.Chat, allforiwch eich data fel JSON yn \"My Data\" a dewiswch y ffeil .zip y mae'n ei hanfon atoch, neu ffeil .json wedi'i hallforio o un ystafell. Mae pob ystafell yn dod yn gerdyn a'i negeseuon yn dod yn sylwadau'r cerdyn, fel bod y wedd Chat yn dangos yr ystafell. Mae'r .zip y mae WeKan yn ei allforio ar gyfer mewnforiwr CSV Rocket.Chat yn cael ei ddarllen hefyd.",
"import-board-instruction-evernote": "Yn Evernote, allforiwch y nodiadau neu lyfr nodiadau fel ffeil .enex a dewiswch hi yma, neu gludwch ei thestun. Mae pob nodyn yn dod yn gerdyn gyda'i destun, ei flychau ticio tasgau fel rhestr wirio, ei dagiau fel labeli a'i nodyn atgoffa fel y dyddiad cwblhau; mae nodiadau y mae eu nodyn atgoffa wedi'i wneud yn mynd i Done. Nid yw delweddau a ffeiliau atodedig yn cael eu mewnforio.",
"tool-group-kanban": "Offer Kanban a phrosiectau",
"tool-group-issues": "Tracwyr problemau a rheoli fersiynau",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Åbn projektets Issues i Redmine, vælg Also available in: CSV nederst på listen, vælg kolonnerne (All columns med Description), og eksportér. Indsæt derefter CSV-filen. Redmine navngiver kolonnerne på dit sprog, så indstil sproget til English i My account før eksporten. Hver status bliver til en liste, og sager bliver til kort med sagstypen som etiket, tildelt person, forfatter, datoer, overordnet opgave og relaterede sager; prioritet, kategori, målversion, estimeret tid, % Done og brugerdefinerede felter bliver til brugerdefinerede felter.",
"import-board-instruction-notion": "Åbn databasen som en hel side i Notion, vælg ••• og Export, vælg Markdown & CSV, og vælg den hentede .zip-fil, eller én database-CSV fra den, eller indsæt den CSV-fil. En kolonne med navnet Status bestemmer listerne (hvis den mangler, bruges den første kolonne, der ligner et valgfelt, og importrapporten fortæller hvilken). Rækker bliver til kort med titel, tags som etiketter, personer som medlemmer, datoer og sidens tekst som beskrivelse; andre kolonner bliver til brugerdefinerede felter. Relationer, billeder og vedhæftninger importeres ikke.",
"import-board-instruction-plane": "Åbn Workspace Settings i Plane, vælg Exports, eksportér projekterne som JSON, CSV eller Excel, og hent .zip-filen. Vælg derefter filen, eller én fil fra den, eller indsæt JSON eller CSV. Statusser bliver til lister, projekter bliver til svømmebaner, og sager bliver til kort med identifikator, overordnet sag, tildelte personer, etiketter, datoer, links og kommentarer; prioritet, estimat, cyklus og modul bliver til brugerdefinerede felter. Planes eksport indeholder ingen beskrivelser eller vedhæftninger, så de importeres ikke.",
"import-board-instruction-fizzy": "I Fizzy skal du eksportere kontoen i \"Account settings\" eller dine egne kort med \"Download my data\" og vælge den .zip-fil, Fizzy sender dig, eller ét korts .json-fil. Tavler bliver til svømmebaner, og kolonner bliver til lister, med \"Maybe?\", \"Not now\" og \"Done\" som i Fizzy; kort beholder deres beskrivelse, etiketter, tildelte personer, trin som en tjekliste, kommentarer og filer.",
"import-board-instruction-mail": "Vælg en .mbox-fil, som Thunderbird, Apple Mail, mutt eller Gmail via Google Takeout gemmer den, eller en enkelt .eml-besked, eller indsæt dens tekst. Hver samtale bliver ét kort i listen Inbox, med afsender, modtagere og emne, så den vises i Email-visningen; svarene bliver dens kommentarer. Gmail-etiketter bliver til etiketter. Vedhæftede filer importeres ikke.",
"import-board-instruction-ical": "Vælg en .ics-kalenderfil, som Google Calendar, Apple Calendar eller Reminders, Thunderbird, Nextcloud eller Outlook eksporterer den, eller indsæt dens tekst. Opgaver går til To Do, In Progress, Done eller Cancelled efter deres status, og begivenheder til Events, med start- og forfaldsdato, så de vises i Calendar- og Gantt-visningerne. Kategorier og prioritet bliver til etiketter. Gentagne elementer importeres én gang.",
"import-board-instruction-googletakeout": "Vælg på takeout.google.com Tasks, Keep, Mail, Calendar og Google Chat, opret eksporten og download .zip-filen, og vælg den derefter her. Hvert produkt bliver en svømmebane: mail til Email-visningen, opgavelister og noter med deres tjeklister, kalenderbegivenheder og opgaver med datoer, og chatrum hvis beskeder er kommentarer til Chat-visningen. Andre produkter og vedhæftede filer importeres ikke.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Åbn i Telegram Desktop Settings, Advanced, Export Telegram data, vælg formatet JSON og eksportér, og vælg derefter filen result.json, eller indsæt dens tekst. Hver chat bliver et kort i Direct messages, Groups eller Channels, og dens beskeder bliver kortets kommentarer, så Chat-visningen viser chatten. Billeder og filer importeres ikke.",
"import-board-instruction-whatsapp": "Åbn chatten i WhatsApp, vælg Export chat uden medier, og vælg .txt-filen her, eller indsæt dens tekst. Chatten bliver et kort, hvis beskeder er dets kommentarer, efter afsender og tidspunkt, så Chat-visningen viser den. Medier og systembeskeder importeres ikke.",
"import-board-instruction-discord": "Eksportér en Discord-kanal med DiscordChatExporter i formatet JSON og vælg .json-filen, eller indsæt dens tekst. Kanalen bliver et kort i sin kategori, og dens beskeder bliver kortets kommentarer, så Chat-visningen viser kanalen. Serveren bliver svømmebanen. Vedhæftede filer importeres ikke.",
"import-board-instruction-rocketchat": "I Rocket.Chat skal du eksportere dine data som JSON i \"My Data\" og vælge den .zip-fil, du får tilsendt, eller ét rums eksporterede .json-fil. Hvert rum bliver et kort, og dets beskeder bliver kortets kommentarer, så Chat-visningen viser rummet. Den .zip, som WeKan eksporterer til Rocket.Chats CSV-importør, kan også læses.",
"import-board-instruction-evernote": "Eksportér i Evernote noterne eller en notesbog som en .enex-fil og vælg den her, eller indsæt dens tekst. Hver note bliver et kort med sin tekst, sine afkrydsningsfelter som en tjekliste, sine tags som etiketter og sin påmindelse som forfaldsdato; noter hvis påmindelse er udført, går til Done. Billeder og vedhæftede filer importeres ikke.",
"tool-group-kanban": "Kanban- og projektværktøjer",
"tool-group-issues": "Fejlsporing og versionsstyring",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Öffne in Redmine die Issues des Projekts, wähle unten in der Liste Also available in: CSV, wähle die Spalten (All columns mit Description) und exportiere sie. Füge dann die CSV-Datei ein. Redmine benennt die Spalten in deiner Sprache; stelle daher vor dem Export unter My account deine Sprache auf English. Jeder Status wird zu einer Liste und Issues werden zu Karten, mit dem Tracker als Label, zugewiesener Person, Autor, Datumsangaben, übergeordneter Aufgabe und verknüpften Issues; Priorität, Kategorie, Zielversion, geschätzte Zeit, % Done und benutzerdefinierte Felder werden zu benutzerdefinierten Feldern.",
"import-board-instruction-notion": "Öffne in Notion die Datenbank als ganze Seite, wähle ••• und Export, dann Markdown & CSV. Wähle die heruntergeladene .zip-Datei oder eine darin enthaltene Datenbank-CSV aus oder füge diese CSV ein. Eine Spalte namens Status wird zu Listen (fehlt sie, wird die erste Spalte verwendet, die wie eine Auswahl aussieht; der Importbericht nennt sie). Zeilen werden zu Karten mit Titel, Tags als Labels, Personen als Mitgliedern, Datumsangaben und dem Seitentext als Beschreibung; andere Spalten werden zu benutzerdefinierten Feldern. Beziehungen, Bilder und Anhänge werden nicht importiert.",
"import-board-instruction-plane": "Öffne in Plane Workspace Settings, wähle Exports, exportiere die Projekte als JSON, CSV oder Excel und lade die .zip-Datei herunter. Wähle diese Datei oder eine darin enthaltene Datei aus oder füge das JSON oder die CSV ein. Statuswerte werden zu Listen, Projekte zu Swimlanes und Issues zu Karten mit Kennung, übergeordnetem Eintrag, zugewiesenen Personen, Labels, Datumsangaben, Links und Kommentaren; Priorität, Schätzung, Zyklus und Modul werden zu benutzerdefinierten Feldern. Der Export von Plane enthält keine Beschreibungen oder Anhänge; sie werden daher nicht importiert.",
"import-board-instruction-fizzy": "Exportieren Sie in Fizzy das Konto unter „Account settings“ oder Ihre eigenen Karten mit „Download my data“, und wählen Sie die .zip-Datei, die Fizzy Ihnen sendet, oder die .json-Datei einer Karte. Tafeln werden zu Arbeitsbahnen und Spalten zu Listen, mit „Maybe?“, „Not now“ und „Done“ wie in Fizzy; Karten behalten ihre Beschreibung, Kennzeichnungen, zugewiesenen Personen, Schritte als Checkliste, Kommentare und Dateien.",
"import-board-instruction-mail": "Wählen Sie eine .mbox-Datei, wie Thunderbird, Apple Mail, mutt oder Gmail über Google Takeout sie speichern, oder eine einzelne .eml-Nachricht, oder fügen Sie ihren Text ein. Jede Unterhaltung wird zu einer Karte in der Liste Inbox, mit Absender, Empfängern und Betreff, sodass sie in der Ansicht Email erscheint; die Antworten werden zu ihren Kommentaren. Gmail-Labels werden zu Kennzeichnungen. Anhänge werden nicht importiert.",
"import-board-instruction-ical": "Wählen Sie eine .ics-Kalenderdatei, wie Google Calendar, Apple Calendar oder Reminders, Thunderbird, Nextcloud oder Outlook sie exportieren, oder fügen Sie ihren Text ein. Aufgaben kommen je nach Status in To Do, In Progress, Done oder Cancelled, und Termine in Events, mit ihrem Start- und Fälligkeitsdatum, sodass sie in den Ansichten Calendar und Gantt erscheinen. Kategorien und Priorität werden zu Kennzeichnungen. Wiederkehrende Einträge werden einmal importiert.",
"import-board-instruction-googletakeout": "Wählen Sie auf takeout.google.com Tasks, Keep, Mail, Calendar und Google Chat aus, erstellen Sie den Export und laden Sie die .zip-Datei herunter, und wählen Sie sie dann hier. Jedes Produkt wird zu einer Arbeitsbahn: Mail für die Ansicht Email, Aufgabenlisten und Notizen mit ihren Checklisten, Kalendertermine und Aufgaben mit Datum, und Chat-Bereiche, deren Nachrichten Kommentare für die Ansicht Chat sind. Andere Produkte und Anhänge werden nicht importiert.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Öffnen Sie in Telegram Desktop Settings, Advanced, Export Telegram data, wählen Sie das Format JSON und exportieren Sie, und wählen Sie dann die Datei result.json, oder fügen Sie ihren Text ein. Jeder Chat wird zu einer Karte in Direct messages, Groups oder Channels, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Chat zeigt. Fotos und Dateien werden nicht importiert.",
"import-board-instruction-whatsapp": "Öffnen Sie in WhatsApp den Chat, wählen Sie Export chat ohne Medien und wählen Sie hier die .txt-Datei, oder fügen Sie ihren Text ein. Der Chat wird zu einer Karte, deren Nachrichten ihre Kommentare sind, nach Absender und Zeit, sodass die Ansicht Chat ihn zeigt. Medien und Systemnachrichten werden nicht importiert.",
"import-board-instruction-discord": "Exportieren Sie einen Discord-Kanal mit DiscordChatExporter im Format JSON und wählen Sie die .json-Datei, oder fügen Sie ihren Text ein. Der Kanal wird zu einer Karte in seiner Kategorie, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Kanal zeigt. Der Server wird zur Arbeitsbahn. Anhänge werden nicht importiert.",
"import-board-instruction-rocketchat": "Exportieren Sie in Rocket.Chat Ihre Daten unter „My Data“ als JSON, und wählen Sie die .zip-Datei, die Sie erhalten, oder die exportierte .json-Datei eines Raums. Jeder Raum wird zu einer Karte, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Raum zeigt. Die .zip-Datei, die WeKan für den CSV-Importer von Rocket.Chat exportiert, wird ebenfalls gelesen.",
"import-board-instruction-evernote": "Exportieren Sie in Evernote die Notizen oder ein Notizbuch als .enex-Datei und wählen Sie sie hier, oder fügen Sie ihren Text ein. Jede Notiz wird zu einer Karte mit ihrem Text, ihren To-do-Kästchen als Checkliste, ihren Tags als Kennzeichnungen und ihrer Erinnerung als Fälligkeitsdatum; Notizen, deren Erinnerung erledigt ist, kommen in Done. Bilder und angehängte Dateien werden nicht importiert.",
"tool-group-kanban": "Kanban- und Projektwerkzeuge",
"tool-group-issues": "Issue-Tracker und Versionskontrolle",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Öffne in Redmine die Issues des Projekts, wähle unten in der Liste Also available in: CSV, wähle die Spalten (All columns mit Description) und exportiere sie. Füge dann die CSV-Datei ein. Redmine benennt die Spalten in deiner Sprache; stelle daher vor dem Export unter My account deine Sprache auf English. Jeder Status wird zu einer Liste und Issues werden zu Karten, mit dem Tracker als Label, zugewiesener Person, Autor, Datumsangaben, übergeordneter Aufgabe und verknüpften Issues; Priorität, Kategorie, Zielversion, geschätzte Zeit, % Done und benutzerdefinierte Felder werden zu benutzerdefinierten Feldern.",
"import-board-instruction-notion": "Öffne in Notion die Datenbank als ganze Seite, wähle ••• und Export, dann Markdown & CSV. Wähle die heruntergeladene .zip-Datei oder eine darin enthaltene Datenbank-CSV aus oder füge diese CSV ein. Eine Spalte namens Status wird zu Listen (fehlt sie, wird die erste Spalte verwendet, die wie eine Auswahl aussieht; der Importbericht nennt sie). Zeilen werden zu Karten mit Titel, Tags als Labels, Personen als Mitgliedern, Datumsangaben und dem Seitentext als Beschreibung; andere Spalten werden zu benutzerdefinierten Feldern. Beziehungen, Bilder und Anhänge werden nicht importiert.",
"import-board-instruction-plane": "Öffne in Plane Workspace Settings, wähle Exports, exportiere die Projekte als JSON, CSV oder Excel und lade die .zip-Datei herunter. Wähle diese Datei oder eine darin enthaltene Datei aus oder füge das JSON oder die CSV ein. Statuswerte werden zu Listen, Projekte zu Swimlanes und Issues zu Karten mit Kennung, übergeordnetem Eintrag, zugewiesenen Personen, Labels, Datumsangaben, Links und Kommentaren; Priorität, Schätzung, Zyklus und Modul werden zu benutzerdefinierten Feldern. Der Export von Plane enthält keine Beschreibungen oder Anhänge; sie werden daher nicht importiert.",
"import-board-instruction-fizzy": "Exportieren Sie in Fizzy das Konto unter «Account settings» oder Ihre eigenen Karten mit «Download my data», und wählen Sie die .zip-Datei, die Fizzy Ihnen sendet, oder die .json-Datei einer Karte. Tafeln werden zu Arbeitsbahnen und Spalten zu Listen, mit «Maybe?», «Not now» und «Done» wie in Fizzy; Karten behalten ihre Beschreibung, Kennzeichnungen, zugewiesenen Personen, Schritte als Checkliste, Kommentare und Dateien.",
"import-board-instruction-mail": "Wählen Sie eine .mbox-Datei, wie Thunderbird, Apple Mail, mutt oder Gmail über Google Takeout sie speichern, oder eine einzelne .eml-Nachricht, oder fügen Sie ihren Text ein. Jede Unterhaltung wird zu einer Karte in der Liste Inbox, mit Absender, Empfängern und Betreff, sodass sie in der Ansicht Email erscheint; die Antworten werden zu ihren Kommentaren. Gmail-Labels werden zu Kennzeichnungen. Anhänge werden nicht importiert.",
"import-board-instruction-ical": "Wählen Sie eine .ics-Kalenderdatei, wie Google Calendar, Apple Calendar oder Reminders, Thunderbird, Nextcloud oder Outlook sie exportieren, oder fügen Sie ihren Text ein. Aufgaben kommen je nach Status in To Do, In Progress, Done oder Cancelled, und Termine in Events, mit ihrem Start- und Fälligkeitsdatum, sodass sie in den Ansichten Calendar und Gantt erscheinen. Kategorien und Priorität werden zu Kennzeichnungen. Wiederkehrende Einträge werden einmal importiert.",
"import-board-instruction-googletakeout": "Wählen Sie auf takeout.google.com Tasks, Keep, Mail, Calendar und Google Chat aus, erstellen Sie den Export und laden Sie die .zip-Datei herunter, und wählen Sie sie dann hier. Jedes Produkt wird zu einer Arbeitsbahn: Mail für die Ansicht Email, Aufgabenlisten und Notizen mit ihren Checklisten, Kalendertermine und Aufgaben mit Datum, und Chat-Bereiche, deren Nachrichten Kommentare für die Ansicht Chat sind. Andere Produkte und Anhänge werden nicht importiert.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Öffnen Sie in Telegram Desktop Settings, Advanced, Export Telegram data, wählen Sie das Format JSON und exportieren Sie, und wählen Sie dann die Datei result.json, oder fügen Sie ihren Text ein. Jeder Chat wird zu einer Karte in Direct messages, Groups oder Channels, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Chat zeigt. Fotos und Dateien werden nicht importiert.",
"import-board-instruction-whatsapp": "Öffnen Sie in WhatsApp den Chat, wählen Sie Export chat ohne Medien und wählen Sie hier die .txt-Datei, oder fügen Sie ihren Text ein. Der Chat wird zu einer Karte, deren Nachrichten ihre Kommentare sind, nach Absender und Zeit, sodass die Ansicht Chat ihn zeigt. Medien und Systemnachrichten werden nicht importiert.",
"import-board-instruction-discord": "Exportieren Sie einen Discord-Kanal mit DiscordChatExporter im Format JSON und wählen Sie die .json-Datei, oder fügen Sie ihren Text ein. Der Kanal wird zu einer Karte in seiner Kategorie, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Kanal zeigt. Der Server wird zur Arbeitsbahn. Anhänge werden nicht importiert.",
"import-board-instruction-rocketchat": "Exportieren Sie in Rocket.Chat Ihre Daten unter «My Data» als JSON, und wählen Sie die .zip-Datei, die Sie erhalten, oder die exportierte .json-Datei eines Raums. Jeder Raum wird zu einer Karte, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Raum zeigt. Die .zip-Datei, die WeKan für den CSV-Importer von Rocket.Chat exportiert, wird ebenfalls gelesen.",
"import-board-instruction-evernote": "Exportieren Sie in Evernote die Notizen oder ein Notizbuch als .enex-Datei und wählen Sie sie hier, oder fügen Sie ihren Text ein. Jede Notiz wird zu einer Karte mit ihrem Text, ihren To-do-Kästchen als Checkliste, ihren Tags als Kennzeichnungen und ihrer Erinnerung als Fälligkeitsdatum; Notizen, deren Erinnerung erledigt ist, kommen in Done. Bilder und angehängte Dateien werden nicht importiert.",
"tool-group-kanban": "Kanban- und Projektwerkzeuge",
"tool-group-issues": "Issue-Tracker und Versionsverwaltung",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Öffne in Redmine die Issues des Projekts, wähle unten in der Liste Also available in: CSV, wähle die Spalten (All columns mit Description) und exportiere sie. Füge dann die CSV-Datei ein. Redmine benennt die Spalten in deiner Sprache; stelle daher vor dem Export unter My account deine Sprache auf English. Jeder Status wird zu einer Liste und Issues werden zu Karten, mit dem Tracker als Label, zugewiesener Person, Autor, Datumsangaben, übergeordneter Aufgabe und verknüpften Issues; Priorität, Kategorie, Zielversion, geschätzte Zeit, % Done und benutzerdefinierte Felder werden zu benutzerdefinierten Feldern.",
"import-board-instruction-notion": "Öffne in Notion die Datenbank als ganze Seite, wähle ••• und Export, dann Markdown & CSV. Wähle die heruntergeladene .zip-Datei oder eine darin enthaltene Datenbank-CSV aus oder füge diese CSV ein. Eine Spalte namens Status wird zu Listen (fehlt sie, wird die erste Spalte verwendet, die wie eine Auswahl aussieht; der Importbericht nennt sie). Zeilen werden zu Karten mit Titel, Tags als Labels, Personen als Mitgliedern, Datumsangaben und dem Seitentext als Beschreibung; andere Spalten werden zu benutzerdefinierten Feldern. Beziehungen, Bilder und Anhänge werden nicht importiert.",
"import-board-instruction-plane": "Öffne in Plane Workspace Settings, wähle Exports, exportiere die Projekte als JSON, CSV oder Excel und lade die .zip-Datei herunter. Wähle diese Datei oder eine darin enthaltene Datei aus oder füge das JSON oder die CSV ein. Statuswerte werden zu Listen, Projekte zu Swimlanes und Issues zu Karten mit Kennung, übergeordnetem Eintrag, zugewiesenen Personen, Labels, Datumsangaben, Links und Kommentaren; Priorität, Schätzung, Zyklus und Modul werden zu benutzerdefinierten Feldern. Der Export von Plane enthält keine Beschreibungen oder Anhänge; sie werden daher nicht importiert.",
"import-board-instruction-fizzy": "Exportieren Sie in Fizzy das Konto unter „Account settings“ oder Ihre eigenen Karten mit „Download my data“, und wählen Sie die .zip-Datei, die Fizzy Ihnen sendet, oder die .json-Datei einer Karte. Tafeln werden zu Arbeitsbahnen und Spalten zu Listen, mit „Maybe?“, „Not now“ und „Done“ wie in Fizzy; Karten behalten ihre Beschreibung, Kennzeichnungen, zugewiesenen Personen, Schritte als Checkliste, Kommentare und Dateien.",
"import-board-instruction-mail": "Wählen Sie eine .mbox-Datei, wie Thunderbird, Apple Mail, mutt oder Gmail über Google Takeout sie speichern, oder eine einzelne .eml-Nachricht, oder fügen Sie ihren Text ein. Jede Unterhaltung wird zu einer Karte in der Liste Inbox, mit Absender, Empfängern und Betreff, sodass sie in der Ansicht Email erscheint; die Antworten werden zu ihren Kommentaren. Gmail-Labels werden zu Kennzeichnungen. Anhänge werden nicht importiert.",
"import-board-instruction-ical": "Wählen Sie eine .ics-Kalenderdatei, wie Google Calendar, Apple Calendar oder Reminders, Thunderbird, Nextcloud oder Outlook sie exportieren, oder fügen Sie ihren Text ein. Aufgaben kommen je nach Status in To Do, In Progress, Done oder Cancelled, und Termine in Events, mit ihrem Start- und Fälligkeitsdatum, sodass sie in den Ansichten Calendar und Gantt erscheinen. Kategorien und Priorität werden zu Kennzeichnungen. Wiederkehrende Einträge werden einmal importiert.",
"import-board-instruction-googletakeout": "Wählen Sie auf takeout.google.com Tasks, Keep, Mail, Calendar und Google Chat aus, erstellen Sie den Export und laden Sie die .zip-Datei herunter, und wählen Sie sie dann hier. Jedes Produkt wird zu einer Arbeitsbahn: Mail für die Ansicht Email, Aufgabenlisten und Notizen mit ihren Checklisten, Kalendertermine und Aufgaben mit Datum, und Chat-Bereiche, deren Nachrichten Kommentare für die Ansicht Chat sind. Andere Produkte und Anhänge werden nicht importiert.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Öffnen Sie in Telegram Desktop Settings, Advanced, Export Telegram data, wählen Sie das Format JSON und exportieren Sie, und wählen Sie dann die Datei result.json, oder fügen Sie ihren Text ein. Jeder Chat wird zu einer Karte in Direct messages, Groups oder Channels, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Chat zeigt. Fotos und Dateien werden nicht importiert.",
"import-board-instruction-whatsapp": "Öffnen Sie in WhatsApp den Chat, wählen Sie Export chat ohne Medien und wählen Sie hier die .txt-Datei, oder fügen Sie ihren Text ein. Der Chat wird zu einer Karte, deren Nachrichten ihre Kommentare sind, nach Absender und Zeit, sodass die Ansicht Chat ihn zeigt. Medien und Systemnachrichten werden nicht importiert.",
"import-board-instruction-discord": "Exportieren Sie einen Discord-Kanal mit DiscordChatExporter im Format JSON und wählen Sie die .json-Datei, oder fügen Sie ihren Text ein. Der Kanal wird zu einer Karte in seiner Kategorie, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Kanal zeigt. Der Server wird zur Arbeitsbahn. Anhänge werden nicht importiert.",
"import-board-instruction-rocketchat": "Exportieren Sie in Rocket.Chat Ihre Daten unter „My Data“ als JSON, und wählen Sie die .zip-Datei, die Sie erhalten, oder die exportierte .json-Datei eines Raums. Jeder Raum wird zu einer Karte, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Raum zeigt. Die .zip-Datei, die WeKan für den CSV-Importer von Rocket.Chat exportiert, wird ebenfalls gelesen.",
"import-board-instruction-evernote": "Exportieren Sie in Evernote die Notizen oder ein Notizbuch als .enex-Datei und wählen Sie sie hier, oder fügen Sie ihren Text ein. Jede Notiz wird zu einer Karte mit ihrem Text, ihren To-do-Kästchen als Checkliste, ihren Tags als Kennzeichnungen und ihrer Erinnerung als Fälligkeitsdatum; Notizen, deren Erinnerung erledigt ist, kommen in Done. Bilder und angehängte Dateien werden nicht importiert.",
"tool-group-kanban": "Kanban- und Projektwerkzeuge",
"tool-group-issues": "Issue-Tracker und Versionsverwaltung",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Öffne in Redmine die Issues des Projekts, wähle unten in der Liste Also available in: CSV, wähle die Spalten (All columns mit Description) und exportiere sie. Füge dann die CSV-Datei ein. Redmine benennt die Spalten in deiner Sprache; stelle daher vor dem Export unter My account deine Sprache auf English. Jeder Status wird zu einer Liste und Issues werden zu Karten, mit dem Tracker als Label, zugewiesener Person, Autor, Datumsangaben, übergeordneter Aufgabe und verknüpften Issues; Priorität, Kategorie, Zielversion, geschätzte Zeit, % Done und benutzerdefinierte Felder werden zu benutzerdefinierten Feldern.",
"import-board-instruction-notion": "Öffne in Notion die Datenbank als ganze Seite, wähle ••• und Export, dann Markdown & CSV. Wähle die heruntergeladene .zip-Datei oder eine darin enthaltene Datenbank-CSV aus oder füge diese CSV ein. Eine Spalte namens Status wird zu Listen (fehlt sie, wird die erste Spalte verwendet, die wie eine Auswahl aussieht; der Importbericht nennt sie). Zeilen werden zu Karten mit Titel, Tags als Labels, Personen als Mitgliedern, Datumsangaben und dem Seitentext als Beschreibung; andere Spalten werden zu benutzerdefinierten Feldern. Beziehungen, Bilder und Anhänge werden nicht importiert.",
"import-board-instruction-plane": "Öffne in Plane Workspace Settings, wähle Exports, exportiere die Projekte als JSON, CSV oder Excel und lade die .zip-Datei herunter. Wähle diese Datei oder eine darin enthaltene Datei aus oder füge das JSON oder die CSV ein. Statuswerte werden zu Listen, Projekte zu Swimlanes und Issues zu Karten mit Kennung, übergeordnetem Eintrag, zugewiesenen Personen, Labels, Datumsangaben, Links und Kommentaren; Priorität, Schätzung, Zyklus und Modul werden zu benutzerdefinierten Feldern. Der Export von Plane enthält keine Beschreibungen oder Anhänge; sie werden daher nicht importiert.",
"import-board-instruction-fizzy": "Exportieren Sie in Fizzy das Konto unter „Account settings“ oder Ihre eigenen Karten mit „Download my data“, und wählen Sie die .zip-Datei, die Fizzy Ihnen sendet, oder die .json-Datei einer Karte. Tafeln werden zu Arbeitsbahnen und Spalten zu Listen, mit „Maybe?“, „Not now“ und „Done“ wie in Fizzy; Karten behalten ihre Beschreibung, Kennzeichnungen, zugewiesenen Personen, Schritte als Checkliste, Kommentare und Dateien.",
"import-board-instruction-mail": "Wählen Sie eine .mbox-Datei, wie Thunderbird, Apple Mail, mutt oder Gmail über Google Takeout sie speichern, oder eine einzelne .eml-Nachricht, oder fügen Sie ihren Text ein. Jede Unterhaltung wird zu einer Karte in der Liste Inbox, mit Absender, Empfängern und Betreff, sodass sie in der Ansicht Email erscheint; die Antworten werden zu ihren Kommentaren. Gmail-Labels werden zu Kennzeichnungen. Anhänge werden nicht importiert.",
"import-board-instruction-ical": "Wählen Sie eine .ics-Kalenderdatei, wie Google Calendar, Apple Calendar oder Reminders, Thunderbird, Nextcloud oder Outlook sie exportieren, oder fügen Sie ihren Text ein. Aufgaben kommen je nach Status in To Do, In Progress, Done oder Cancelled, und Termine in Events, mit ihrem Start- und Fälligkeitsdatum, sodass sie in den Ansichten Calendar und Gantt erscheinen. Kategorien und Priorität werden zu Kennzeichnungen. Wiederkehrende Einträge werden einmal importiert.",
"import-board-instruction-googletakeout": "Wählen Sie auf takeout.google.com Tasks, Keep, Mail, Calendar und Google Chat aus, erstellen Sie den Export und laden Sie die .zip-Datei herunter, und wählen Sie sie dann hier. Jedes Produkt wird zu einer Arbeitsbahn: Mail für die Ansicht Email, Aufgabenlisten und Notizen mit ihren Checklisten, Kalendertermine und Aufgaben mit Datum, und Chat-Bereiche, deren Nachrichten Kommentare für die Ansicht Chat sind. Andere Produkte und Anhänge werden nicht importiert.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Öffnen Sie in Telegram Desktop Settings, Advanced, Export Telegram data, wählen Sie das Format JSON und exportieren Sie, und wählen Sie dann die Datei result.json, oder fügen Sie ihren Text ein. Jeder Chat wird zu einer Karte in Direct messages, Groups oder Channels, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Chat zeigt. Fotos und Dateien werden nicht importiert.",
"import-board-instruction-whatsapp": "Öffnen Sie in WhatsApp den Chat, wählen Sie Export chat ohne Medien und wählen Sie hier die .txt-Datei, oder fügen Sie ihren Text ein. Der Chat wird zu einer Karte, deren Nachrichten ihre Kommentare sind, nach Absender und Zeit, sodass die Ansicht Chat ihn zeigt. Medien und Systemnachrichten werden nicht importiert.",
"import-board-instruction-discord": "Exportieren Sie einen Discord-Kanal mit DiscordChatExporter im Format JSON und wählen Sie die .json-Datei, oder fügen Sie ihren Text ein. Der Kanal wird zu einer Karte in seiner Kategorie, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Kanal zeigt. Der Server wird zur Arbeitsbahn. Anhänge werden nicht importiert.",
"import-board-instruction-rocketchat": "Exportieren Sie in Rocket.Chat Ihre Daten unter „My Data“ als JSON, und wählen Sie die .zip-Datei, die Sie erhalten, oder die exportierte .json-Datei eines Raums. Jeder Raum wird zu einer Karte, und seine Nachrichten werden zu den Kommentaren der Karte, sodass die Ansicht Chat den Raum zeigt. Die .zip-Datei, die WeKan für den CSV-Importer von Rocket.Chat exportiert, wird ebenfalls gelesen.",
"import-board-instruction-evernote": "Exportieren Sie in Evernote die Notizen oder ein Notizbuch als .enex-Datei und wählen Sie sie hier, oder fügen Sie ihren Text ein. Jede Notiz wird zu einer Karte mit ihrem Text, ihren To-do-Kästchen als Checkliste, ihren Tags als Kennzeichnungen und ihrer Erinnerung als Fälligkeitsdatum; Notizen, deren Erinnerung erledigt ist, kommen in Done. Bilder und angehängte Dateien werden nicht importiert.",
"tool-group-kanban": "Kanban- und Projektwerkzeuge",
"tool-group-issues": "Issue-Tracker und Versionskontrolle",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Redmine ནང་ ལས་འགུལ་གྱི་ Issues ཁ་ཕྱེ་ ཐོ་ཡིག་གི་མཇུག་ལུ་ Also available in: CSV གདམ་ ཀ་ཐིག་ཚུ་ (All columns, Description དང་གཅིག་ཁར་) གདམ་ཞིནམ་ལས་ ཕྱིར་སྐྱེལ་འབད་ དེ་ལས་ CSV འདི་སྦྱར། Redmine གིས་ ཀ་ཐིག་ཚུ་ཁྱོད་ཀྱི་སྐད་ཡིག་ནང་མིང་བཏགསཔ་ཨིན་ དེ་འབདཝ་ལས་ ཕྱིར་སྐྱེལ་མ་འབད་བའི་ཧེ་མ་ My account ནང་ ཁྱོད་ཀྱི་སྐད་ཡིག་འདི་ ཨིང་ལིཤ་ལུ་གཞི་སྒྲིག་འབད། གནས་སྟངས་རེ་རེ་ ཐོ་ཡིག་ལུ་འགྱུར་ཏེ་ གནད་དོན་ཚུ་ tracker འདི་ཁ་ཡིག་སྦེ་, འགན་འཁུར་པ་, རྩོམ་པ་པོ་, ཚེས་གྲངས་, ཕ་མའི་ལས་འགན་དང་ འབྲེལ་བ་ཡོད་པའི་གནད་དོན་དང་གཅིག་ཁར་ ཤོག་བྱང་ལུ་འགྱུརཝ་ཨིན། གཙོ་རིམ་, དབྱེ་ཁག་, དམིགས་གཏད་ཐོན་རིམ་, ཚོད་རྩིས་དུས་ཚོད་, % Done དང་ སྒེར་གྱི་ས་སྒོ་ཚུ་ སྒེར་གྱི་ས་སྒོ་ལུ་འགྱུརཝ་ཨིན།",
"import-board-instruction-notion": "Notion ནང་ གནད་སྡུད་གཞི་རྟེན་འདི་ ཤོག་ལེབ་ཧྲིལ་བུམ་སྦེ་ཁ་ཕྱེ་ ••• དང་ Export གདམ་ Markdown & CSV གདམ་ཞིནམ་ལས་ ཕབ་ལེན་འབད་མི་ .zip ཡིག་སྣོད་ ཡང་ན་ དེ་གི་ནང་ལས་ གནད་སྡུད་གཞི་རྟེན་ CSV ཅིག་གདམ་ ཡང་ན་ CSV དེ་སྦྱར། Status ཟེར་མིང་བཏགས་མི་ཀ་ཐིག་ཅིག་ ཐོ་ཡིག་ལུ་འགྱུརཝ་ཨིན་ (དེ་མེད་པ་ཅིན་ select བཟུམ་སྦེ་མཐོང་མི་ཀ་ཐིག་དང་པ་འདི་ ནང་འདྲེན་སྙན་ཞུ་ནང་ག་འདི་ཨིན་ན་སྟོནམ་ཨིན་)། གྲལ་ཐིག་ཚུ་ མགོ་མིང་, ཁ་ཡིག་, མི་ཚུ་འཐུས་མི་སྦེ་, ཚེས་གྲངས་དང་ ཤོག་ལེབ་ཀྱི་ཚིག་ཡིག་འདི་འགྲེལ་བཤད་སྦེ་ ཤོག་བྱང་ལུ་འགྱུརཝ་ཨིན། ཀ་ཐིག་གཞན་ཚུ་ སྒེར་གྱི་ས་སྒོ་ལུ་འགྱུརཝ་ཨིན། འབྲེལ་བ་, པར་དང་ མཉམ་སྦྲགས་ཚུ་ནང་འདྲེན་མི་འབད།",
"import-board-instruction-plane": "Plane ནང་ Workspace Settings ཁ་ཕྱེ་ Exports གདམ་ ལས་འགུལ་ཚུ་ JSON, CSV ཡང་ན་ Excel སྦེ་ཕྱིར་སྐྱེལ་འབད་ .zip ཡིག་སྣོད་ཕབ་ལེན་འབད་ དེ་ལས་ ཡིག་སྣོད་དེ་ ཡང་ན་ དེ་གི་ནང་གི་ཡིག་སྣོད་ཅིག་གདམ་ ཡང་ན་ JSON ཡང་ན་ CSV སྦྱར། གནས་སྟངས་ཚུ་ཐོ་ཡིག་ལུ་ ལས་འགུལ་ཚུ་ཆུ་ལམ་ལུ་ དེ་ལས་ གནད་དོན་ཚུ་ ངོས་འཛིན་, ཕ་མ་, འགན་འཁུར་པ་, ཁ་ཡིག་, ཚེས་གྲངས་, འབྲེལ་མཐུད་དང་ བསམ་བཀོད་དང་གཅིག་ཁར་ ཤོག་བྱང་ལུ་འགྱུརཝ་ཨིན། གཙོ་རིམ་, ཚོད་རྩིས་, འཁོར་རིམ་དང་ module ཚུ་ སྒེར་གྱི་ས་སྒོ་ལུ་འགྱུརཝ་ཨིན། Plane གི་ཕྱིར་སྐྱེལ་ནང་ འགྲེལ་བཤད་དང་མཉམ་སྦྲགས་མེདཔ་ལས་ དེ་ཚུ་ནང་འདྲེན་མི་འབད།",
"import-board-instruction-fizzy": "Fizzy ནང་ \"Account settings\" ནང་ རྩིས་ཐོ་ ཕྱིར་བསྐྱལ་འབད་ ཡང་ན་ \"Download my data\" གིས་ རང་གི་ཤོག་བྱང་ཚུ་ ཕྱིར་བསྐྱལ་འབད་སྟེ་ Fizzy གིས་གཏང་མི་ .zip ཡིག་ཆ་ ཡང་ན་ ཤོག་བྱང་གཅིག་གི་ .json ཡིག་ཆ་ གདམ་ཁ་རྐྱབ། པད་ཤིང་ཚུ་ ལམ་ལུ་འགྱུརཝ་ཨིན་ ཀ་ཐིག་ཚུ་ ཐོ་ཡིག་ལུ་འགྱུརཝ་ཨིན་ \"Maybe?\", \"Not now\" དང་ \"Done\" ཚུ་ Fizzy ནང་བཞིན་ཨིན། ཤོག་བྱང་ཚུ་གིས་ འགྲེལ་བཤད་, ཁ་ཡིག་, འགན་འབག་མི་, ཞིབ་དཔྱད་ཐོ་ཡིག་སྦེ་ གོ་རིམ་, བསམ་འཆར་དང་ ཡིག་ཆ་ཚུ་ བཞགཔ་ཨིན།",
"import-board-instruction-mail": "Thunderbird, Apple Mail, mutt ཡང་ན་ Google Takeout བརྒྱུད་དེ་ Gmail གིས་སྲུང་བཞག་འབད་མི་ .mbox ཡིག་ཆ་ཅིག་ ཡང་ན་ .eml འཕྲིན་ཡིག་གཅིག་ གདམ་ཁ་རྐྱབ་ ཡང་ན་ དེའི་ཡི་གེ་སྦྱར། གླེང་མོལ་རེ་རེ་ གཏང་མི་ ལེན་མི་དང་ བརྗོད་གཞི་དང་གཅིག་ཁར་ Inbox ཐོ་ཡིག་ནང་ ཤོག་བྱང་གཅིག་ལུ་འགྱུརཝ་ཨིན་ དེ་འབདཝ་ལས་ Email མཐོང་སྣང་ནང་སྟོནམ་ཨིན། ལན་ཚུ་ དེའི་བསམ་འཆར་ལུ་འགྱུརཝ་ཨིན། Gmail གི་ཁ་ཡིག་ཚུ་ ཁ་ཡིག་ལུ་འགྱུརཝ་ཨིན། མཉམ་སྦྲགས་ཚུ་ ནང་བསྐྱལ་མི་འབད།",
"import-board-instruction-ical": "Google Calendar, Apple Calendar ཡང་ན་ Reminders, Thunderbird, Nextcloud ཡང་ན་ Outlook གིས་ཕྱིར་བསྐྱལ་འབད་མི་ .ics ཟླ་ཐོའི་ཡིག་ཆ་ཅིག་ གདམ་ཁ་རྐྱབ་ ཡང་ན་ དེའི་ཡི་གེ་སྦྱར། ལཱ་ཚུ་ ཁོང་གི་གནས་སྟངས་ལྟར་ To Do, In Progress, Done ཡང་ན་ Cancelled ནང་འགྱོཝ་ཨིན་ ལས་རིམ་ཚུ་ Events ནང་འགྱོཝ་ཨིན་ འགོ་བཙུགས་ཚེས་དང་ དུས་ཚོད་ཚེས་དང་གཅིག་ཁར་ དེ་འབདཝ་ལས་ Calendar དང་ Gantt མཐོང་སྣང་ནང་སྟོནམ་ཨིན། སྡེ་ཚན་དང་ གཙོ་རིམ་ཚུ་ ཁ་ཡིག་ལུ་འགྱུརཝ་ཨིན། ལོག་ལོག་འབྱུང་བའི་རྣམ་གྲངས་ཚུ་ ཚར་གཅིག་ནང་བསྐྱལ་འབདཝ་ཨིན།",
"import-board-instruction-googletakeout": "takeout.google.com ནང་ Tasks, Keep, Mail, Calendar དང་ Google Chat གདམ་ཁ་རྐྱབ་ ཕྱིར་བསྐྱལ་བཟོ་སྟེ་ .zip ཡིག་ཆ་ཕབ་ལེན་འབད་ དེ་ལས་ ནཱ་ལུ་གདམ་ཁ་རྐྱབ། ཐོན་སྐྱེད་རེ་རེ་ ལམ་གཅིག་ལུ་འགྱུརཝ་ཨིན། Email མཐོང་སྣང་གི་དོན་ལུ་ གློག་འཕྲིན་ ཞིབ་དཔྱད་ཐོ་ཡིག་དང་གཅིག་ཁར་ ལཱ་གི་ཐོ་ཡིག་དང་ དྲན་ཐོ་ ཚེས་གྲངས་དང་གཅིག་ཁར་ ཟླ་ཐོའི་ལས་རིམ་དང་ ལཱ་ དེ་ལས་ འཕྲིན་ཡིག་ཚུ་ Chat མཐོང་སྣང་གི་བསམ་འཆར་ཨིན་མི་ གླེང་མོལ་གྱི་ས་སྟོང་ཚུ། ཐོན་སྐྱེད་གཞན་དང་ མཉམ་སྦྲགས་ཚུ་ ནང་བསྐྱལ་མི་འབད།",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Telegram Desktop ནང་ Settings, Advanced, Export Telegram data ཁ་ཕྱེ་ JSON རྣམ་པ་གདམ་ཁ་རྐྱབ་སྟེ་ ཕྱིར་བསྐྱལ་འབད་ དེ་ལས་ result.json ཡིག་ཆ་གདམ་ཁ་རྐྱབ་ ཡང་ན་ དེའི་ཡི་གེ་སྦྱར། གླེང་མོལ་རེ་རེ་ Direct messages, Groups ཡང་ན་ Channels ནང་ ཤོག་བྱང་གཅིག་ལུ་འགྱུརཝ་ཨིན་ དེའི་འཕྲིན་ཡིག་ཚུ་ ཤོག་བྱང་གི་བསམ་འཆར་ལུ་འགྱུརཝ་ཨིན་ དེ་འབདཝ་ལས་ Chat མཐོང་སྣང་གིས་ གླེང་མོལ་སྟོནམ་ཨིན། པར་དང་ ཡིག་ཆ་ཚུ་ ནང་བསྐྱལ་མི་འབད།",
"import-board-instruction-whatsapp": "WhatsApp ནང་ གླེང་མོལ་ཁ་ཕྱེ་ བརྡ་ལམ་མེད་པར་ Export chat གདམ་ཁ་རྐྱབ་སྟེ་ ནཱ་ལུ་ .txt ཡིག་ཆ་གདམ་ཁ་རྐྱབ་ ཡང་ན་ དེའི་ཡི་གེ་སྦྱར། གླེང་མོལ་དེ་ ཤོག་བྱང་གཅིག་ལུ་འགྱུརཝ་ཨིན་ དེའི་འཕྲིན་ཡིག་ཚུ་ གཏང་མི་དང་ ཆུ་ཚོད་ལྟར་ དེའི་བསམ་འཆར་ཨིན་ དེ་འབདཝ་ལས་ Chat མཐོང་སྣང་གིས་ དེ་སྟོནམ་ཨིན། བརྡ་ལམ་དང་ རིམ་ལུགས་ཀྱི་འཕྲིན་ཡིག་ཚུ་ ནང་བསྐྱལ་མི་འབད།",
"import-board-instruction-discord": "DiscordChatExporter གིས་ Discord རྒྱུ་ལམ་ཅིག་ JSON རྣམ་པའི་ནང་ ཕྱིར་བསྐྱལ་འབད་སྟེ་ .json ཡིག་ཆ་གདམ་ཁ་རྐྱབ་ ཡང་ན་ དེའི་ཡི་གེ་སྦྱར། རྒྱུ་ལམ་དེ་ དེའི་སྡེ་ཚན་ནང་ ཤོག་བྱང་གཅིག་ལུ་འགྱུརཝ་ཨིན་ དེའི་འཕྲིན་ཡིག་ཚུ་ ཤོག་བྱང་གི་བསམ་འཆར་ལུ་འགྱུརཝ་ཨིན་ དེ་འབདཝ་ལས་ Chat མཐོང་སྣང་གིས་ རྒྱུ་ལམ་སྟོནམ་ཨིན། ཞབས་ཞུ་ཆས་དེ་ ལམ་ལུ་འགྱུརཝ་ཨིན། མཉམ་སྦྲགས་ཚུ་ ནང་བསྐྱལ་མི་འབད།",
"import-board-instruction-rocketchat": "Rocket.Chat ནང་ \"My Data\" ནང་ ཁྱོད་ཀྱི་གནད་སྡུད་ JSON སྦེ་ ཕྱིར་བསྐྱལ་འབད་སྟེ་ དེ་གིས་གཏང་མི་ .zip ཡིག་ཆ་ ཡང་ན་ ཁང་མིག་གཅིག་གི་ ཕྱིར་བསྐྱལ་འབད་ཡོད་པའི་ .json ཡིག་ཆ་ གདམ་ཁ་རྐྱབ། ཁང་མིག་རེ་རེ་ ཤོག་བྱང་གཅིག་ལུ་འགྱུརཝ་ཨིན་ དེའི་འཕྲིན་ཡིག་ཚུ་ ཤོག་བྱང་གི་བསམ་འཆར་ལུ་འགྱུརཝ་ཨིན་ དེ་འབདཝ་ལས་ Chat མཐོང་སྣང་གིས་ ཁང་མིག་སྟོནམ་ཨིན། WeKan གིས་ Rocket.Chat གི་ CSV ནང་འདྲེན་ཆས་ཀྱི་དོན་ལུ་ ཕྱིར་བསྐྱལ་འབད་མི་ .zip ཡང་ ལྷག་ཚུགས།",
"import-board-instruction-evernote": "Evernote ནང་ དྲན་ཐོ་ཚུ་ ཡང་ན་ དྲན་དེབ་ཅིག་ .enex ཡིག་ཆ་སྦེ་ ཕྱིར་བསྐྱལ་འབད་སྟེ་ ནཱ་ལུ་གདམ་ཁ་རྐྱབ་ ཡང་ན་ དེའི་ཡི་གེ་སྦྱར། དྲན་ཐོ་རེ་རེ་ ཤོག་བྱང་གཅིག་ལུ་འགྱུརཝ་ཨིན་ དེའི་ཡི་གེ་དང་ འབད་དགོ་པའི་རྟགས་སྒྲོམ་ཚུ་ ཞིབ་དཔྱད་ཐོ་ཡིག་སྦེ་ དེའི་རྟགས་ཚུ་ ཁ་ཡིག་སྦེ་ དེ་ལས་ དྲན་སྐུལ་དེ་ དུས་ཚོད་ཚེས་སྦེ། དྲན་སྐུལ་མཇུག་བསྡུ་ཡོད་པའི་དྲན་ཐོ་ཚུ་ Done ནང་འགྱོཝ་ཨིན། པར་དང་ མཉམ་སྦྲགས་ཡིག་ཆ་ཚུ་ ནང་བསྐྱལ་མི་འབད།",
"tool-group-kanban": "Kanban དང་ལས་འགུལ་གྱི་ལག་ཆས",
"tool-group-issues": "དཀའ་ངལ་རྗེས་འདེད་དང་ཐོན་རིམ་ཚད་འཛིན",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Le Redmine me la, ʋu dɔ la ƒe Issues, tia Also available in: CSV le xexlẽdzesi la ƒe te, tia ƒlowo (All columns, kple Description) eye nàɖee, emegbe tsɔ CSV la de eme. Redmine naa ŋkɔ ƒlowo le wò gbe me, eyata ɖo wò gbe be wòanye Eŋlisigbe le My account me hafi nàɖee. Nɔnɔme ɖesiaɖe zua xexlẽdzesi eye nyawo zua kaɖiwo, kple tracker abe dzesi ene, dɔwɔla, ŋlɔla, ŋkekewo, dɔ dzitsotso kple nya siwo do ka; priority, category, target version, estimated time, % Done kple agble tɔxɛwo zua agble tɔxɛwo.",
"import-board-instruction-notion": "Le Notion me la, ʋu nyatakakadzraɖoƒe la abe axa blibo ene, tia ••• kple Export, tia Markdown & CSV, eye nàtia .zip faɛl si wòxɔ, alo nyatakakadzraɖoƒe CSV ɖeka tso eme, alo tsɔ CSV ma de eme. Ƒlo si ŋkɔ nye Status la zua xexlẽdzesiwo (ne eya meli o la, ƒlo gbãtɔ si dze abe tiatia ene la zuna, eye nuxɔxɔ ƒe nyatakaka gblɔa esi wònye); fliwo zua kaɖiwo kple woƒe ŋkɔ, tags abe dzesiwo ene, amewo abe dzolawo ene, ŋkekewo, kple axa ƒe nuŋɔŋlɔ abe numeɖeɖe ene; ƒlo bubuwo zua agble tɔxɛwo. Wometsɔa kadodowo, nɔnɔmetatawo kple nu siwo wokpe ɖe eŋu vaa eme o.",
"import-board-instruction-plane": "Le Plane me la, ʋu Workspace Settings, tia Exports, ɖe dɔwo abe JSON, CSV alo Excel ene eye nàxɔ .zip faɛl la, emegbe tia faɛl ma, alo faɛl ɖeka si le eme, alo tsɔ JSON alo CSV la de eme. Nɔnɔmewo zua xexlẽdzesiwo, dɔwo zua tsiƒuƒuwo, eye nyawo zua kaɖiwo kple woƒe dzesidenu, dzitsotso, dɔwɔlawo, dzesiwo, ŋkekewo, kadodowo kple nyaŋuɖoɖowo; priority, estimate, cycle kple module zua agble tɔxɛwo. Numeɖeɖe alo nu siwo wokpe ɖe eŋu aɖeke mele Plane ƒe ɖeɖe me o, eyata wometsɔa wo vaa eme o.",
"import-board-instruction-fizzy": "Le Fizzy me la, ɖe akɔnta la le \"Account settings\" me, alo wò ŋutɔ wò agbalẽviwo kple \"Download my data\", eye nàtia .zip faɛl si Fizzy aɖo ɖe wò, alo agbalẽvi ɖeka ƒe .json faɛl. Ŋɔŋlɔkpewo zua mɔwo, eye tsitreƒewo zua xexlẽdzesiwo, kple \"Maybe?\", \"Not now\" kple \"Done\" abe le Fizzy me ene; agbalẽviwo léa woƒe numeɖeɖe, dzesiwo, dɔwɔlawo, afɔɖeɖewo abe dodokpɔ xexlẽdzesi ene, nuŋɔŋlɔwo kple faɛlwo ɖe asi.",
"import-board-instruction-mail": "Tia .mbox agbalẽ, abe ale si Thunderbird, Apple Mail, mutt alo Gmail to Google Takeout dzi dzraa wo ɖo ene, alo .eml gbedasi ɖeka, alo tsɔ eƒe nuŋɔŋlɔ de afisia. Dzeɖoɖo ɖesiaɖe zua agbalẽvi ɖeka le xexlẽdzesi Inbox me, kple amesi ɖoe, amesiwo wòɖo na kple eƒe tanya, ale be wòadze le Email kpɔkpɔ me; ŋuɖoɖowo zua eƒe nuŋɔŋlɔwo. Gmail ƒe dzesiwo zua dzesiwo. Nu siwo wotsɔ kpe ɖe eŋu la, womatsɔ wo ava eme o.",
"import-board-instruction-ical": "Tia .ics kalenda agbalẽ, abe ale si Google Calendar, Apple Calendar alo Reminders, Thunderbird, Nextcloud alo Outlook doa goe ene, alo tsɔ eƒe nuŋɔŋlɔ de afisia. Dɔwo yia To Do, In Progress, Done alo Cancelled me le woƒe nɔnɔme nu, eye nudzɔdzɔwo yia Events me, kple woƒe gɔmedzeŋkeke kple ŋkeke mamlɛtɔ, ale be woadze le Calendar kple Gantt kpɔkpɔwo me. Hatsotsowo kple vevienyenye zua dzesiwo. Nu siwo gbugbɔna va la, wotsɔa wo vaa eme zi ɖeka.",
"import-board-instruction-googletakeout": "Le takeout.google.com dzi la, tia Tasks, Keep, Mail, Calendar kple Google Chat, wɔ dodo la eye nàtsɔ .zip agbalẽ la ɖe anyi, emegbe tiae le afisia. Nudzɔdzɔ ɖesiaɖe zua mɔ: lɛta na Email kpɔkpɔ, dɔ ƒe xexlẽdzesiwo kple nuŋlɔɖiwo kple woƒe dodokpɔ xexlẽdzesiwo, kalenda ƒe nudzɔdzɔwo kple dɔwo kple ŋkekewo, kple dzeɖoɖo teƒe siwo ƒe gbedasiwo nye nuŋɔŋlɔwo na Chat kpɔkpɔ. Nudzɔdzɔ bubuwo kple nu siwo wotsɔ kpe ɖe eŋu la, womatsɔ wo ava eme o.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Le Telegram Desktop me la, ʋu Settings, Advanced, Export Telegram data, tia JSON ɖoɖo eye nàdoe goe, emegbe tia result.json agbalẽ la, alo tsɔ eƒe nuŋɔŋlɔ de afisia. Dzeɖoɖo ɖesiaɖe zua agbalẽvi le Direct messages, Groups alo Channels me, eye eƒe gbedasiwo zua agbalẽvi la ƒe nuŋɔŋlɔwo, ale be Chat kpɔkpɔ naɖe dzeɖoɖo la afia. Foto kple agbalẽwo, womatsɔ wo ava eme o.",
"import-board-instruction-whatsapp": "Le WhatsApp me la, ʋu dzeɖoɖo la, tia Export chat si me foto kple video mele o, eye nàtia .txt agbalẽ la le afisia, alo tsɔ eƒe nuŋɔŋlɔ de afisia. Dzeɖoɖo la zua agbalẽvi si ƒe gbedasiwo nye eƒe nuŋɔŋlɔwo, le amesi ɖoe kple ɣeyiɣi nu, ale be Chat kpɔkpɔ naɖee afia. Foto kple video kple ɖoɖo ƒe gbedasiwo, womatsɔ wo ava eme o.",
"import-board-instruction-discord": "Do Discord mɔ goe kple DiscordChatExporter le JSON ɖoɖo me eye nàtia .json agbalẽ la, alo tsɔ eƒe nuŋɔŋlɔ de afisia. Mɔ la zua agbalẽvi le eƒe hatsotso me, eye eƒe gbedasiwo zua agbalẽvi la ƒe nuŋɔŋlɔwo, ale be Chat kpɔkpɔ naɖe mɔ la afia. Dɔdzikpɔla la zua mɔ la. Nu siwo wotsɔ kpe ɖe eŋu la, womatsɔ wo ava eme o.",
"import-board-instruction-rocketchat": "Le Rocket.Chat me la, ɖe wò nyatakakawo abe JSON ene le \"My Data\" me eye nàtia .zip faɛl si woaɖo ɖe wò, alo xɔ ɖeka ƒe .json faɛl si woɖe. Xɔ ɖesiaɖe zua agbalẽvi, eye eƒe gbedasiwo zua agbalẽvi la ƒe nuŋɔŋlɔwo, ale be Chat kpɔkpɔ naɖe xɔ la afia. Woxlẽa .zip si WeKan ɖena na Rocket.Chat ƒe CSV xɔla hã.",
"import-board-instruction-evernote": "Le Evernote me la, do nuŋlɔɖiwo alo nuŋlɔɖigbalẽ goe abe .enex agbalẽ ene eye nàtiae le afisia, alo tsɔ eƒe nuŋɔŋlɔ de afisia. Nuŋlɔɖi ɖesiaɖe zua agbalẽvi kple eƒe nuŋɔŋlɔ, eƒe dɔ ƒe dzesigoewo abe dodokpɔ xexlẽdzesi ene, eƒe tagwo abe dzesiwo ene kple eƒe ŋkuɖodzinya abe ŋkeke mamlɛtɔ ene; nuŋlɔɖi siwo ƒe ŋkuɖodzinya wu enu la yia Done me. Nɔnɔmetatawo kple agbalẽ siwo wotsɔ kpe ɖe eŋu la, womatsɔ wo ava eme o.",
"tool-group-kanban": "Kanban kple dɔwɔwɔ ƒe dɔwɔnuwo",
"tool-group-issues": "Kuxiwo ŋuti dzikpɔlawo kple tɔtrɔ ƒe dzikpɔkpɔ",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Στο Redmine, ανοίξτε το Issues του έργου, επιλέξτε Also available in: CSV στο κάτω μέρος της λίστας, επιλέξτε τις στήλες (All columns, μαζί με Description) και κάντε εξαγωγή, έπειτα επικολλήστε το CSV. Το Redmine ονομάζει τις στήλες στη γλώσσα σας, γι' αυτό πριν από την εξαγωγή ορίστε τη γλώσσα σε English στο My account. Κάθε κατάσταση γίνεται λίστα και τα ζητήματα γίνονται κάρτες με τον τύπο ζητήματος ως ετικέτα, το άτομο στο οποίο έχουν ανατεθεί, τον συντάκτη, τις ημερομηνίες, τη γονική εργασία και τα σχετικά ζητήματα· η προτεραιότητα, η κατηγορία, η έκδοση-στόχος, ο εκτιμώμενος χρόνος, το % Done και τα προσαρμοσμένα πεδία γίνονται προσαρμοσμένα πεδία.",
"import-board-instruction-notion": "Στο Notion, ανοίξτε τη βάση δεδομένων ως πλήρη σελίδα, επιλέξτε ••• και Export, επιλέξτε Markdown & CSV και διαλέξτε το αρχείο .zip που κατεβαίνει ή ένα CSV βάσης δεδομένων από αυτό, ή επικολλήστε αυτό το CSV. Μια στήλη με το όνομα Status καθορίζει τις λίστες (αν δεν υπάρχει, χρησιμοποιείται η πρώτη στήλη που μοιάζει με πεδίο επιλογής και η αναφορά εισαγωγής αναφέρει ποια). Οι γραμμές γίνονται κάρτες με τον τίτλο, τις ετικέτες, τα άτομα ως μέλη, τις ημερομηνίες και το κείμενο της σελίδας ως περιγραφή· οι υπόλοιπες στήλες γίνονται προσαρμοσμένα πεδία. Οι σχέσεις, οι εικόνες και τα συνημμένα δεν εισάγονται.",
"import-board-instruction-plane": "Στο Plane, ανοίξτε Workspace Settings, επιλέξτε Exports, εξαγάγετε τα έργα ως JSON, CSV ή Excel και κατεβάστε το αρχείο .zip, έπειτα επιλέξτε αυτό το αρχείο ή ένα αρχείο από το εσωτερικό του, ή επικολλήστε το JSON ή το CSV. Οι καταστάσεις γίνονται λίστες, τα έργα γίνονται διάδρομοι και τα ζητήματα γίνονται κάρτες με το αναγνωριστικό, το γονικό ζήτημα, τα άτομα στα οποία έχουν ανατεθεί, τις ετικέτες, τις ημερομηνίες, τους συνδέσμους και τα σχόλια· η προτεραιότητα, η εκτίμηση, ο κύκλος και η ενότητα γίνονται προσαρμοσμένα πεδία. Η εξαγωγή του Plane δεν περιέχει περιγραφές ή συνημμένα, επομένως αυτά δεν εισάγονται.",
"import-board-instruction-fizzy": "Στο Fizzy, εξαγάγετε τον λογαριασμό από τις «Account settings» ή τις δικές σας κάρτες με το «Download my data» και επιλέξτε το αρχείο .zip που σας στέλνει το Fizzy, ή το αρχείο .json μιας κάρτας. Οι πίνακες γίνονται διάδρομοι και οι στήλες γίνονται λίστες, με τα «Maybe?», «Not now» και «Done» όπως στο Fizzy· οι κάρτες διατηρούν την περιγραφή, τις ετικέτες, τους υπεύθυνους, τα βήματα ως check-list, τα σχόλια και τα αρχεία τους.",
"import-board-instruction-mail": "Επιλέξτε ένα αρχείο .mbox, όπως το αποθηκεύουν το Thunderbird, το Apple Mail, το mutt ή το Gmail μέσω του Google Takeout, ή ένα μεμονωμένο μήνυμα .eml, ή επικολλήστε το κείμενό του. Κάθε συνομιλία γίνεται μία κάρτα στη λίστα Inbox, με τον αποστολέα, τους παραλήπτες και το θέμα της, ώστε να εμφανίζεται στην προβολή Email· οι απαντήσεις γίνονται σχόλιά της. Οι ετικέτες του Gmail γίνονται ετικέτες. Τα συνημμένα δεν εισάγονται.",
"import-board-instruction-ical": "Επιλέξτε ένα αρχείο ημερολογίου .ics, όπως το εξάγουν το Google Calendar, το Apple Calendar ή το Reminders, το Thunderbird, το Nextcloud ή το Outlook, ή επικολλήστε το κείμενό του. Οι εργασίες πηγαίνουν στις To Do, In Progress, Done ή Cancelled ανάλογα με την κατάστασή τους, και τα συμβάντα στη Events, με τις ημερομηνίες έναρξης και προθεσμίας τους, ώστε να εμφανίζονται στις προβολές Calendar και Gantt. Οι κατηγορίες και η προτεραιότητα γίνονται ετικέτες. Τα επαναλαμβανόμενα στοιχεία εισάγονται μία φορά.",
"import-board-instruction-googletakeout": "Στο takeout.google.com, επιλέξτε Tasks, Keep, Mail, Calendar και Google Chat, δημιουργήστε την εξαγωγή και κατεβάστε το αρχείο .zip, και μετά επιλέξτε το εδώ. Κάθε προϊόν γίνεται ένας διάδρομος: η αλληλογραφία για την προβολή Email, οι λίστες εργασιών και οι σημειώσεις με τις check-list τους, τα συμβάντα ημερολογίου και οι εργασίες με ημερομηνίες, και οι χώροι συνομιλίας των οποίων τα μηνύματα είναι σχόλια για την προβολή Chat. Άλλα προϊόντα και τα συνημμένα δεν εισάγονται.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Στο Telegram Desktop, ανοίξτε Settings, Advanced, Export Telegram data, επιλέξτε τη μορφή JSON και εξαγάγετε, και μετά επιλέξτε το αρχείο result.json, ή επικολλήστε το κείμενό του. Κάθε συνομιλία γίνεται μια κάρτα στα Direct messages, Groups ή Channels, και τα μηνύματά της γίνονται σχόλια της κάρτας, ώστε η προβολή Chat να δείχνει τη συνομιλία. Οι φωτογραφίες και τα αρχεία δεν εισάγονται.",
"import-board-instruction-whatsapp": "Στο WhatsApp, ανοίξτε τη συνομιλία, επιλέξτε Export chat χωρίς πολυμέσα, και επιλέξτε εδώ το αρχείο .txt, ή επικολλήστε το κείμενό του. Η συνομιλία γίνεται μια κάρτα της οποίας τα μηνύματα είναι τα σχόλιά της, ανά αποστολέα και ώρα, ώστε η προβολή Chat να τη δείχνει. Τα πολυμέσα και τα μηνύματα συστήματος δεν εισάγονται.",
"import-board-instruction-discord": "Εξαγάγετε ένα κανάλι του Discord με το DiscordChatExporter σε μορφή JSON και επιλέξτε το αρχείο .json, ή επικολλήστε το κείμενό του. Το κανάλι γίνεται μια κάρτα στην κατηγορία του, και τα μηνύματά του γίνονται σχόλια της κάρτας, ώστε η προβολή Chat να δείχνει το κανάλι. Ο διακομιστής γίνεται ο διάδρομος. Τα συνημμένα δεν εισάγονται.",
"import-board-instruction-rocketchat": "Στο Rocket.Chat, εξαγάγετε τα δεδομένα σας ως JSON από το «My Data» και επιλέξτε το αρχείο .zip που σας στέλνει, ή το εξαγόμενο αρχείο .json ενός δωματίου. Κάθε δωμάτιο γίνεται μια κάρτα και τα μηνύματά του γίνονται σχόλια της κάρτας, ώστε η προβολή Chat να δείχνει το δωμάτιο. Διαβάζεται επίσης το .zip που εξάγει το WeKan για τον εισαγωγέα CSV του Rocket.Chat.",
"import-board-instruction-evernote": "Στο Evernote, εξαγάγετε τις σημειώσεις ή ένα σημειωματάριο ως αρχείο .enex και επιλέξτε το εδώ, ή επικολλήστε το κείμενό του. Κάθε σημείωση γίνεται μια κάρτα με το κείμενό της, τα πλαίσια ελέγχου εργασιών της ως check-list, τις ετικέτες της ως ετικέτες και την υπενθύμισή της ως ημερομηνία προθεσμίας· οι σημειώσεις των οποίων η υπενθύμιση έχει ολοκληρωθεί πηγαίνουν στη Done. Οι εικόνες και τα συνημμένα αρχεία δεν εισάγονται.",
"tool-group-kanban": "Εργαλεία Kanban και έργων",
"tool-group-issues": "Παρακολούθηση ζητημάτων και έλεγχος εκδόσεων",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "Στο Redmine, ανοίξτε το Issues του έργου, επιλέξτε Also available in: CSV στο κάτω μέρος της λίστας, επιλέξτε τις στήλες (All columns, μαζί με Description) και κάντε εξαγωγή, έπειτα επικολλήστε το CSV. Το Redmine ονομάζει τις στήλες στη γλώσσα σας, γι' αυτό πριν από την εξαγωγή ορίστε τη γλώσσα σε English στο My account. Κάθε κατάσταση γίνεται λίστα και τα ζητήματα γίνονται κάρτες με τον τύπο ζητήματος ως ετικέτα, το άτομο στο οποίο έχουν ανατεθεί, τον συντάκτη, τις ημερομηνίες, τη γονική εργασία και τα σχετικά ζητήματα· η προτεραιότητα, η κατηγορία, η έκδοση-στόχος, ο εκτιμώμενος χρόνος, το % Done και τα προσαρμοσμένα πεδία γίνονται προσαρμοσμένα πεδία.",
"import-board-instruction-notion": "Στο Notion, ανοίξτε τη βάση δεδομένων ως πλήρη σελίδα, επιλέξτε ••• και Export, επιλέξτε Markdown & CSV και διαλέξτε το αρχείο .zip που κατεβαίνει ή ένα CSV βάσης δεδομένων από αυτό, ή επικολλήστε αυτό το CSV. Μια στήλη με το όνομα Status καθορίζει τις λίστες (αν δεν υπάρχει, χρησιμοποιείται η πρώτη στήλη που μοιάζει με πεδίο επιλογής και η αναφορά εισαγωγής αναφέρει ποια). Οι γραμμές γίνονται κάρτες με τον τίτλο, τις ετικέτες, τα άτομα ως μέλη, τις ημερομηνίες και το κείμενο της σελίδας ως περιγραφή· οι υπόλοιπες στήλες γίνονται προσαρμοσμένα πεδία. Οι σχέσεις, οι εικόνες και τα συνημμένα δεν εισάγονται.",
"import-board-instruction-plane": "Στο Plane, ανοίξτε Workspace Settings, επιλέξτε Exports, εξαγάγετε τα έργα ως JSON, CSV ή Excel και κατεβάστε το αρχείο .zip, έπειτα επιλέξτε αυτό το αρχείο ή ένα αρχείο από το εσωτερικό του, ή επικολλήστε το JSON ή το CSV. Οι καταστάσεις γίνονται λίστες, τα έργα γίνονται διάδρομοι και τα ζητήματα γίνονται κάρτες με το αναγνωριστικό, το γονικό ζήτημα, τα άτομα στα οποία έχουν ανατεθεί, τις ετικέτες, τις ημερομηνίες, τους συνδέσμους και τα σχόλια· η προτεραιότητα, η εκτίμηση, ο κύκλος και η ενότητα γίνονται προσαρμοσμένα πεδία. Η εξαγωγή του Plane δεν περιέχει περιγραφές ή συνημμένα, επομένως αυτά δεν εισάγονται.",
"import-board-instruction-fizzy": "Στο Fizzy, εξαγάγετε τον λογαριασμό από τις «Account settings» ή τις δικές σας κάρτες με το «Download my data» και επιλέξτε το αρχείο .zip που σας στέλνει το Fizzy, ή το αρχείο .json μιας κάρτας. Οι πίνακες γίνονται διάδρομοι και οι στήλες γίνονται λίστες, με τα «Maybe?», «Not now» και «Done» όπως στο Fizzy· οι κάρτες διατηρούν την περιγραφή, τις ετικέτες, τους υπεύθυνους, τα βήματα ως check-list, τα σχόλια και τα αρχεία τους.",
"import-board-instruction-mail": "Επιλέξτε ένα αρχείο .mbox, όπως το αποθηκεύουν το Thunderbird, το Apple Mail, το mutt ή το Gmail μέσω του Google Takeout, ή ένα μεμονωμένο μήνυμα .eml, ή επικολλήστε το κείμενό του. Κάθε συνομιλία γίνεται μία κάρτα στη λίστα Inbox, με τον αποστολέα, τους παραλήπτες και το θέμα της, ώστε να εμφανίζεται στην προβολή Email· οι απαντήσεις γίνονται σχόλιά της. Οι ετικέτες του Gmail γίνονται ετικέτες. Τα συνημμένα δεν εισάγονται.",
"import-board-instruction-ical": "Επιλέξτε ένα αρχείο ημερολογίου .ics, όπως το εξάγουν το Google Calendar, το Apple Calendar ή το Reminders, το Thunderbird, το Nextcloud ή το Outlook, ή επικολλήστε το κείμενό του. Οι εργασίες πηγαίνουν στις To Do, In Progress, Done ή Cancelled ανάλογα με την κατάστασή τους, και τα συμβάντα στη Events, με τις ημερομηνίες έναρξης και προθεσμίας τους, ώστε να εμφανίζονται στις προβολές Calendar και Gantt. Οι κατηγορίες και η προτεραιότητα γίνονται ετικέτες. Τα επαναλαμβανόμενα στοιχεία εισάγονται μία φορά.",
"import-board-instruction-googletakeout": "Στο takeout.google.com, επιλέξτε Tasks, Keep, Mail, Calendar και Google Chat, δημιουργήστε την εξαγωγή και κατεβάστε το αρχείο .zip, και μετά επιλέξτε το εδώ. Κάθε προϊόν γίνεται ένας διάδρομος: η αλληλογραφία για την προβολή Email, οι λίστες εργασιών και οι σημειώσεις με τις check-list τους, τα συμβάντα ημερολογίου και οι εργασίες με ημερομηνίες, και οι χώροι συνομιλίας των οποίων τα μηνύματα είναι σχόλια για την προβολή Chat. Άλλα προϊόντα και τα συνημμένα δεν εισάγονται.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "Στο Telegram Desktop, ανοίξτε Settings, Advanced, Export Telegram data, επιλέξτε τη μορφή JSON και εξαγάγετε, και μετά επιλέξτε το αρχείο result.json, ή επικολλήστε το κείμενό του. Κάθε συνομιλία γίνεται μια κάρτα στα Direct messages, Groups ή Channels, και τα μηνύματά της γίνονται σχόλια της κάρτας, ώστε η προβολή Chat να δείχνει τη συνομιλία. Οι φωτογραφίες και τα αρχεία δεν εισάγονται.",
"import-board-instruction-whatsapp": "Στο WhatsApp, ανοίξτε τη συνομιλία, επιλέξτε Export chat χωρίς πολυμέσα, και επιλέξτε εδώ το αρχείο .txt, ή επικολλήστε το κείμενό του. Η συνομιλία γίνεται μια κάρτα της οποίας τα μηνύματα είναι τα σχόλιά της, ανά αποστολέα και ώρα, ώστε η προβολή Chat να τη δείχνει. Τα πολυμέσα και τα μηνύματα συστήματος δεν εισάγονται.",
"import-board-instruction-discord": "Εξαγάγετε ένα κανάλι του Discord με το DiscordChatExporter σε μορφή JSON και επιλέξτε το αρχείο .json, ή επικολλήστε το κείμενό του. Το κανάλι γίνεται μια κάρτα στην κατηγορία του, και τα μηνύματά του γίνονται σχόλια της κάρτας, ώστε η προβολή Chat να δείχνει το κανάλι. Ο διακομιστής γίνεται ο διάδρομος. Τα συνημμένα δεν εισάγονται.",
"import-board-instruction-rocketchat": "Στο Rocket.Chat, εξαγάγετε τα δεδομένα σας ως JSON από το «My Data» και επιλέξτε το αρχείο .zip που σας στέλνει, ή το εξαγόμενο αρχείο .json ενός δωματίου. Κάθε δωμάτιο γίνεται μια κάρτα και τα μηνύματά του γίνονται σχόλια της κάρτας, ώστε η προβολή Chat να δείχνει το δωμάτιο. Διαβάζεται επίσης το .zip που εξάγει το WeKan για τον εισαγωγέα CSV του Rocket.Chat.",
"import-board-instruction-evernote": "Στο Evernote, εξαγάγετε τις σημειώσεις ή ένα σημειωματάριο ως αρχείο .enex και επιλέξτε το εδώ, ή επικολλήστε το κείμενό του. Κάθε σημείωση γίνεται μια κάρτα με το κείμενό της, τα πλαίσια ελέγχου εργασιών της ως check-list, τις ετικέτες της ως ετικέτες και την υπενθύμισή της ως ημερομηνία προθεσμίας· οι σημειώσεις των οποίων η υπενθύμιση έχει ολοκληρωθεί πηγαίνουν στη Done. Οι εικόνες και τα συνημμένα αρχεία δεν εισάγονται.",
"tool-group-kanban": "Εργαλεία Kanban και έργων",
"tool-group-issues": "Παρακολούθηση ζητημάτων και έλεγχος εκδόσεων",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "In Redmine, open the project's Issues, choose Also available in: CSV at the bottom of the list, pick the columns (All columns, with Description) and export, then paste the CSV. Redmine names the columns in your language, so set your language to English in My account before exporting. Each status becomes a list and issues become cards, with the tracker as a label, assignee, author, dates, parent task and related issues; priority, category, target version, estimated time, % Done and custom fields become custom fields.",
"import-board-instruction-notion": "In Notion, open the database as a full page, choose ••• and Export, pick Markdown & CSV, and choose the .zip file it downloads, or one database CSV from it, or paste that CSV. A column named Status becomes the lists (without one, the first column that looks like a select does, and the import report says which); rows become cards with their title, tags as labels, people as members, dates, and the page text as the description; other columns become custom fields. Relations, images and attachments are not imported.",
"import-board-instruction-plane": "In Plane, open Workspace Settings, choose Exports, export the projects as JSON, CSV or Excel and download the .zip file, then choose that file, or one file from inside it, or paste the JSON or CSV. States become lists, projects become swimlanes, and issues become cards with their identifier, parent, assignees, labels, dates, links and comments; priority, estimate, cycle and module become custom fields. Plane's export has no descriptions or attachments, so they are not imported.",
"import-board-instruction-fizzy": "In Fizzy, export the account in Account settings, or your own cards with Download my data, and choose the .zip file Fizzy sends you, or one card's .json file. Boards become swimlanes and columns become lists, with Maybe?, Not now and Done as in Fizzy; cards keep their description, tags, assignees, steps as a checklist, comments and files.",
"import-board-instruction-mail": "Choose an .mbox file, as Thunderbird, Apple Mail, mutt or Gmail through Google Takeout save it, or a single .eml message, or paste its text. Each conversation becomes one card in the Inbox list, with its sender, recipients and subject, so it shows in the Email view; the replies become its comments. Gmail labels become labels. Attachments are not imported.",
"import-board-instruction-ical": "Choose an .ics calendar file, as Google Calendar, Apple Calendar or Reminders, Thunderbird, Nextcloud or Outlook export it, or paste its text. Tasks go to To Do, In Progress, Done or Cancelled by their status, and events to Events, with their start and due dates, so they show in the Calendar and Gantt views. Categories and priority become labels. Repeating items are imported once.",
"import-board-instruction-googletakeout": "At takeout.google.com, choose Tasks, Keep, Mail, Calendar and Google Chat, create the export and download the .zip file, then choose it here. Each product becomes a swimlane: mail for the Email view, task lists and notes with their checklists, calendar events and tasks with dates, and chat spaces whose messages are comments for the Chat view. Other products and attachments are not imported.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "In Telegram Desktop, open Settings, Advanced, Export Telegram data, choose the JSON format and export, then choose the result.json file, or paste its text. Each chat becomes a card in Direct messages, Groups or Channels, and its messages become the card's comments, so the Chat view shows the chat. Photos and files are not imported.",
"import-board-instruction-whatsapp": "In WhatsApp, open the chat, choose Export chat without media, and choose the .txt file here, or paste its text. The chat becomes a card whose messages are its comments, by their sender and time, so the Chat view shows it. Media and system messages are not imported.",
"import-board-instruction-discord": "Export a Discord channel with DiscordChatExporter in the JSON format and choose the .json file, or paste its text. The channel becomes a card in its category, and its messages become the card's comments, so the Chat view shows the channel. The server becomes the swimlane. Attachments are not imported.",
"import-board-instruction-rocketchat": "In Rocket.Chat, export your data as JSON in My Data and choose the .zip file it sends you, or one room's exported .json file. Each room becomes a card and its messages become the card's comments, so the Chat view shows the room. The .zip that WeKan exports for Rocket.Chat's CSV importer is read too.",
"import-board-instruction-evernote": "In Evernote, export the notes or a notebook as an .enex file and choose it here, or paste its text. Each note becomes a card with its text, its to-do checkboxes as a checklist, its tags as labels and its reminder as the due date; notes whose reminder is done go to Done. Images and attached files are not imported.",
"tool-group-kanban": "Kanban and project tools",
"tool-group-issues": "Issue trackers and version control",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "In Redmine, open the project's Issues, choose Also available in: CSV at the bottom of the list, pick the columns (All columns, with Description) and export, then paste the CSV. Redmine names the columns in your language, so set your language to English in My account before exporting. Each status becomes a list and issues become cards, with the tracker as a label, assignee, author, dates, parent task and related issues; priority, category, target version, estimated time, % Done and custom fields become custom fields.",
"import-board-instruction-notion": "In Notion, open the database as a full page, choose ••• and Export, pick Markdown & CSV, and choose the .zip file it downloads, or one database CSV from it, or paste that CSV. A column named Status becomes the lists (without one, the first column that looks like a select does, and the import report says which); rows become cards with their title, tags as labels, people as members, dates, and the page text as the description; other columns become custom fields. Relations, images and attachments are not imported.",
"import-board-instruction-plane": "In Plane, open Workspace Settings, choose Exports, export the projects as JSON, CSV or Excel and download the .zip file, then choose that file, or one file from inside it, or paste the JSON or CSV. States become lists, projects become swimlanes, and issues become cards with their identifier, parent, assignees, labels, dates, links and comments; priority, estimate, cycle and module become custom fields. Plane's export has no descriptions or attachments, so they are not imported.",
"import-board-instruction-fizzy": "In Fizzy, export the account in Account settings, or your own cards with Download my data, and choose the .zip file Fizzy sends you, or one card's .json file. Boards become swimlanes and columns become lists, with Maybe?, Not now and Done as in Fizzy; cards keep their description, tags, assignees, steps as a checklist, comments and files.",
"import-board-instruction-mail": "Choose an .mbox file, as Thunderbird, Apple Mail, mutt or Gmail through Google Takeout save it, or a single .eml message, or paste its text. Each conversation becomes one card in the Inbox list, with its sender, recipients and subject, so it shows in the Email view; the replies become its comments. Gmail labels become labels. Attachments are not imported.",
"import-board-instruction-ical": "Choose an .ics calendar file, as Google Calendar, Apple Calendar or Reminders, Thunderbird, Nextcloud or Outlook export it, or paste its text. Tasks go to To Do, In Progress, Done or Cancelled by their status, and events to Events, with their start and due dates, so they show in the Calendar and Gantt views. Categories and priority become labels. Repeating items are imported once.",
"import-board-instruction-googletakeout": "At takeout.google.com, choose Tasks, Keep, Mail, Calendar and Google Chat, create the export and download the .zip file, then choose it here. Each product becomes a swimlane: mail for the Email view, task lists and notes with their checklists, calendar events and tasks with dates, and chat spaces whose messages are comments for the Chat view. Other products and attachments are not imported.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "In Telegram Desktop, open Settings, Advanced, Export Telegram data, choose the JSON format and export, then choose the result.json file, or paste its text. Each chat becomes a card in Direct messages, Groups or Channels, and its messages become the card's comments, so the Chat view shows the chat. Photos and files are not imported.",
"import-board-instruction-whatsapp": "In WhatsApp, open the chat, choose Export chat without media, and choose the .txt file here, or paste its text. The chat becomes a card whose messages are its comments, by their sender and time, so the Chat view shows it. Media and system messages are not imported.",
"import-board-instruction-discord": "Export a Discord channel with DiscordChatExporter in the JSON format and choose the .json file, or paste its text. The channel becomes a card in its category, and its messages become the card's comments, so the Chat view shows the channel. The server becomes the swimlane. Attachments are not imported.",
"import-board-instruction-rocketchat": "In Rocket.Chat, export your data as JSON in My Data and choose the .zip file it sends you, or one room's exported .json file. Each room becomes a card and its messages become the card's comments, so the Chat view shows the room. The .zip that WeKan exports for Rocket.Chat's CSV importer is read too.",
"import-board-instruction-evernote": "In Evernote, export the notes or a notebook as an .enex file and choose it here, or paste its text. Each note becomes a card with its text, its to-do checkboxes as a checklist, its tags as labels and its reminder as the due date; notes whose reminder is done go to Done. Images and attached files are not imported.",
"tool-group-kanban": "Kanban and project tools",
"tool-group-issues": "Issue trackers and version control",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "In Redmine, open the project's Issues, choose Also available in: CSV at the bottom of the list, pick the columns (All columns, with Description) and export, then paste the CSV. Redmine names the columns in your language, so set your language to English in My account before exporting. Each status becomes a list and issues become cards, with the tracker as a label, assignee, author, dates, parent task and related issues; priority, category, target version, estimated time, % Done and custom fields become custom fields.",
"import-board-instruction-notion": "In Notion, open the database as a full page, choose ••• and Export, pick Markdown & CSV, and choose the .zip file it downloads, or one database CSV from it, or paste that CSV. A column named Status becomes the lists (without one, the first column that looks like a select does, and the import report says which); rows become cards with their title, tags as labels, people as members, dates, and the page text as the description; other columns become custom fields. Relations, images and attachments are not imported.",
"import-board-instruction-plane": "In Plane, open Workspace Settings, choose Exports, export the projects as JSON, CSV or Excel and download the .zip file, then choose that file, or one file from inside it, or paste the JSON or CSV. States become lists, projects become swimlanes, and issues become cards with their identifier, parent, assignees, labels, dates, links and comments; priority, estimate, cycle and module become custom fields. Plane's export has no descriptions or attachments, so they are not imported.",
"import-board-instruction-fizzy": "In Fizzy, export the account in Account settings, or your own cards with Download my data, and choose the .zip file Fizzy sends you, or one card's .json file. Boards become swimlanes and columns become lists, with Maybe?, Not now and Done as in Fizzy; cards keep their description, tags, assignees, steps as a checklist, comments and files.",
"import-board-instruction-mail": "Choose an .mbox file, as Thunderbird, Apple Mail, mutt or Gmail through Google Takeout save it, or a single .eml message, or paste its text. Each conversation becomes one card in the Inbox list, with its sender, recipients and subject, so it shows in the Email view; the replies become its comments. Gmail labels become labels. Attachments are not imported.",
"import-board-instruction-ical": "Choose an .ics calendar file, as Google Calendar, Apple Calendar or Reminders, Thunderbird, Nextcloud or Outlook export it, or paste its text. Tasks go to To Do, In Progress, Done or Cancelled by their status, and events to Events, with their start and due dates, so they show in the Calendar and Gantt views. Categories and priority become labels. Repeating items are imported once.",
"import-board-instruction-googletakeout": "At takeout.google.com, choose Tasks, Keep, Mail, Calendar and Google Chat, create the export and download the .zip file, then choose it here. Each product becomes a swimlane: mail for the Email view, task lists and notes with their checklists, calendar events and tasks with dates, and chat spaces whose messages are comments for the Chat view. Other products and attachments are not imported.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "In Telegram Desktop, open Settings, Advanced, Export Telegram data, choose the JSON format and export, then choose the result.json file, or paste its text. Each chat becomes a card in Direct messages, Groups or Channels, and its messages become the card's comments, so the Chat view shows the chat. Photos and files are not imported.",
"import-board-instruction-whatsapp": "In WhatsApp, open the chat, choose Export chat without media, and choose the .txt file here, or paste its text. The chat becomes a card whose messages are its comments, by their sender and time, so the Chat view shows it. Media and system messages are not imported.",
"import-board-instruction-discord": "Export a Discord channel with DiscordChatExporter in the JSON format and choose the .json file, or paste its text. The channel becomes a card in its category, and its messages become the card's comments, so the Chat view shows the channel. The server becomes the swimlane. Attachments are not imported.",
"import-board-instruction-rocketchat": "In Rocket.Chat, export your data as JSON in My Data and choose the .zip file it sends you, or one room's exported .json file. Each room becomes a card and its messages become the card's comments, so the Chat view shows the room. The .zip that WeKan exports for Rocket.Chat's CSV importer is read too.",
"import-board-instruction-evernote": "In Evernote, export the notes or a notebook as an .enex file and choose it here, or paste its text. Each note becomes a card with its text, its to-do checkboxes as a checklist, its tags as labels and its reminder as the due date; notes whose reminder is done go to Done. Images and attached files are not imported.",
"tool-group-kanban": "Kanban and project tools",
"tool-group-issues": "Issue trackers and version control",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "In Redmine, open the project's Issues, choose Also available in: CSV at the bottom of the list, pick the columns (All columns, with Description) and export, then paste the CSV. Redmine names the columns in your language, so set your language to English in My account before exporting. Each status becomes a list and issues become cards, with the tracker as a label, assignee, author, dates, parent task and related issues; priority, category, target version, estimated time, % Done and custom fields become custom fields.",
"import-board-instruction-notion": "In Notion, open the database as a full page, choose ••• and Export, pick Markdown & CSV, and choose the .zip file it downloads, or one database CSV from it, or paste that CSV. A column named Status becomes the lists (without one, the first column that looks like a select does, and the import report says which); rows become cards with their title, tags as labels, people as members, dates, and the page text as the description; other columns become custom fields. Relations, images and attachments are not imported.",
"import-board-instruction-plane": "In Plane, open Workspace Settings, choose Exports, export the projects as JSON, CSV or Excel and download the .zip file, then choose that file, or one file from inside it, or paste the JSON or CSV. States become lists, projects become swimlanes, and issues become cards with their identifier, parent, assignees, labels, dates, links and comments; priority, estimate, cycle and module become custom fields. Plane's export has no descriptions or attachments, so they are not imported.",
"import-board-instruction-fizzy": "In Fizzy, export the account in Account settings, or your own cards with Download my data, and choose the .zip file Fizzy sends you, or one card's .json file. Boards become swimlanes and columns become lists, with Maybe?, Not now and Done as in Fizzy; cards keep their description, tags, assignees, steps as a checklist, comments and files.",
"import-board-instruction-mail": "Choose an .mbox file, as Thunderbird, Apple Mail, mutt or Gmail through Google Takeout save it, or a single .eml message, or paste its text. Each conversation becomes one card in the Inbox list, with its sender, recipients and subject, so it shows in the Email view; the replies become its comments. Gmail labels become labels. Attachments are not imported.",
"import-board-instruction-ical": "Choose an .ics calendar file, as Google Calendar, Apple Calendar or Reminders, Thunderbird, Nextcloud or Outlook export it, or paste its text. Tasks go to To Do, In Progress, Done or Cancelled by their status, and events to Events, with their start and due dates, so they show in the Calendar and Gantt views. Categories and priority become labels. Repeating items are imported once.",
"import-board-instruction-googletakeout": "At takeout.google.com, choose Tasks, Keep, Mail, Calendar and Google Chat, create the export and download the .zip file, then choose it here. Each product becomes a swimlane: mail for the Email view, task lists and notes with their checklists, calendar events and tasks with dates, and chat spaces whose messages are comments for the Chat view. Other products and attachments are not imported.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "In Telegram Desktop, open Settings, Advanced, Export Telegram data, choose the JSON format and export, then choose the result.json file, or paste its text. Each chat becomes a card in Direct messages, Groups or Channels, and its messages become the card's comments, so the Chat view shows the chat. Photos and files are not imported.",
"import-board-instruction-whatsapp": "In WhatsApp, open the chat, choose Export chat without media, and choose the .txt file here, or paste its text. The chat becomes a card whose messages are its comments, by their sender and time, so the Chat view shows it. Media and system messages are not imported.",
"import-board-instruction-discord": "Export a Discord channel with DiscordChatExporter in the JSON format and choose the .json file, or paste its text. The channel becomes a card in its category, and its messages become the card's comments, so the Chat view shows the channel. The server becomes the swimlane. Attachments are not imported.",
"import-board-instruction-rocketchat": "In Rocket.Chat, export your data as JSON in My Data and choose the .zip file it sends you, or one room's exported .json file. Each room becomes a card and its messages become the card's comments, so the Chat view shows the room. The .zip that WeKan exports for Rocket.Chat's CSV importer is read too.",
"import-board-instruction-evernote": "In Evernote, export the notes or a notebook as an .enex file and choose it here, or paste its text. Each note becomes a card with its text, its to-do checkboxes as a checklist, its tags as labels and its reminder as the due date; notes whose reminder is done go to Done. Images and attached files are not imported.",
"tool-group-kanban": "Kanban and project tools",
"tool-group-issues": "Issue trackers and version control",
+2
View File
@@ -954,6 +954,7 @@
"import-board-instruction-redmine": "In Redmine, open the project's Issues, choose Also available in: CSV at the bottom of the list, pick the columns (All columns, with Description) and export, then paste the CSV. Redmine names the columns in your language, so set your language to English in My account before exporting. Each status becomes a list and issues become cards, with the tracker as a label, assignee, author, dates, parent task and related issues; priority, category, target version, estimated time, % Done and custom fields become custom fields.",
"import-board-instruction-notion": "In Notion, open the database as a full page, choose ••• and Export, pick Markdown & CSV, and choose the .zip file it downloads, or one database CSV from it, or paste that CSV. A column named Status becomes the lists (without one, the first column that looks like a select does, and the import report says which); rows become cards with their title, tags as labels, people as members, dates, and the page text as the description; other columns become custom fields. Relations, images and attachments are not imported.",
"import-board-instruction-plane": "In Plane, open Workspace Settings, choose Exports, export the projects as JSON, CSV or Excel and download the .zip file, then choose that file, or one file from inside it, or paste the JSON or CSV. States become lists, projects become swimlanes, and issues become cards with their identifier, parent, assignees, labels, dates, links and comments; priority, estimate, cycle and module become custom fields. Plane's export has no descriptions or attachments, so they are not imported.",
"import-board-instruction-fizzy": "In Fizzy, export the account in Account settings, or your own cards with Download my data, and choose the .zip file Fizzy sends you, or one card's .json file. Boards become swimlanes and columns become lists, with Maybe?, Not now and Done as in Fizzy; cards keep their description, tags, assignees, steps as a checklist, comments and files.",
"import-board-instruction-mail": "Choose an .mbox file, as Thunderbird, Apple Mail, mutt or Gmail through Google Takeout save it, or a single .eml message, or paste its text. Each conversation becomes one card in the Inbox list, with its sender, recipients and subject, so it shows in the Email view; the replies become its comments. Gmail labels become labels. Attachments are not imported.",
"import-board-instruction-ical": "Choose an .ics calendar file, as Google Calendar, Apple Calendar or Reminders, Thunderbird, Nextcloud or Outlook export it, or paste its text. Tasks go to To Do, In Progress, Done or Cancelled by their status, and events to Events, with their start and due dates, so they show in the Calendar and Gantt views. Categories and priority become labels. Repeating items are imported once.",
"import-board-instruction-googletakeout": "At takeout.google.com, choose Tasks, Keep, Mail, Calendar and Google Chat, create the export and download the .zip file, then choose it here. Each product becomes a swimlane: mail for the Email view, task lists and notes with their checklists, calendar events and tasks with dates, and chat spaces whose messages are comments for the Chat view. Other products and attachments are not imported.",
@@ -962,6 +963,7 @@
"import-board-instruction-telegram": "In Telegram Desktop, open Settings, Advanced, Export Telegram data, choose the JSON format and export, then choose the result.json file, or paste its text. Each chat becomes a card in Direct messages, Groups or Channels, and its messages become the card's comments, so the Chat view shows the chat. Photos and files are not imported.",
"import-board-instruction-whatsapp": "In WhatsApp, open the chat, choose Export chat without media, and choose the .txt file here, or paste its text. The chat becomes a card whose messages are its comments, by their sender and time, so the Chat view shows it. Media and system messages are not imported.",
"import-board-instruction-discord": "Export a Discord channel with DiscordChatExporter in the JSON format and choose the .json file, or paste its text. The channel becomes a card in its category, and its messages become the card's comments, so the Chat view shows the channel. The server becomes the swimlane. Attachments are not imported.",
"import-board-instruction-rocketchat": "In Rocket.Chat, export your data as JSON in My Data and choose the .zip file it sends you, or one room's exported .json file. Each room becomes a card and its messages become the card's comments, so the Chat view shows the room. The .zip that WeKan exports for Rocket.Chat's CSV importer is read too.",
"import-board-instruction-evernote": "In Evernote, export the notes or a notebook as an .enex file and choose it here, or paste its text. Each note becomes a card with its text, its to-do checkboxes as a checklist, its tags as labels and its reminder as the due date; notes whose reminder is done go to Done. Images and attached files are not imported.",
"tool-group-kanban": "Kanban and project tools",
"tool-group-issues": "Issue trackers and version control",
Loaded 100 of 405 files, more files were not shown because too many files have changed in this diff. Show more