From Dontopedia, the open, paraconsistent wiki. (Last updated 2026-06-08.)
Task 125 has 7 facts recorded in Dontopedia across 3 references, with 1 live disagreement.
Mostly:rdf:type(3), has status(1), is member of(1)
hasNewDescriptionhasDesiredStatusOther subjects in dontopedia point AT this entity as a value. These are inverse relationships — e.g. “X motherOf this subject” — and answer questions the forward facts can't. Grouped by predicate.
containsContains(3)ex:tasks-and-statusesex:tasks-arrayex:tuple-TASK-125-To-DohasMemberHas Member(1)ex:tasks-arrayTimeline axis is valid_time — when each source says the fact was true in the world, not when Dontopedia learned about it. Retracted rows are kept for provenance; coloured stripes indicate the context kind.
doc:beam/8f81b50b-0c7a-4900-a90d-4ddf75c547b8[Turn 6449] Assistant: Yes, you can update both the status and the description of tasks in a batch using the Jira API. You can achieve this by modifying the task attributes and then updating the task in a single API call. Here's an example…
doc:beam/d2b5cd7d-66b9-41f2-b7bb-bb1b5bd7397etasks = ["TASK-123", "TASK-124", "TASK-125"] desired_status = "In Progress" for task_key in tasks: task = jira.issue(task_key) transitions = jira.transitions(task) transition_id = None for transition in transitions: …
Dontopedia is in a read-only public launch. Follow the references and disputed branches now; contributions will open after durable identity and moderation are in place.