You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now having the distinction between inline and global task references very much improves the way to build-reference smaller tasks inline.
We can now describe a certain feature in within the sentence link to the accomplishing task.
However gaining an overview is still simply done by looking at the margin and see the task-number there.
So I found myself doing both, task:ABC-123[describing the task done inline] while still generating an overview task::ABC-123[].
This feel kind of double-work for the same task. What would improve the situation? I suggest to insert a simple option character to have both:
existing task::ABC-123[] renders right ABC-123
existing task::ABC-123[describing the task done inline] renders right describing the task done inline
existing task:ABC-123[] renders inline ABC-123
existing task:+ABC-123[describing the task done inline] renders inline describing the task done inline
proposaltask:+ABC-123[describing the task done inline] renders inline describing the task done inlineAND right ABC-123
proposaltask:*ABC-123[describing the task done inline] renders inline describing the task done inlineAND right describing the task done inline
I'm open for other suggestions to avoid double-specification of tasks
The text was updated successfully, but these errors were encountered:
Yes, there's a small node app that uses the GitHub API to poll the status of issues. I can add an additional repository without any problem. Setting this up for Jira is a bit more complicated and haven't delved much deeper in recent days.
Now having the distinction between inline and global task references very much improves the way to build-reference smaller tasks inline.
We can now describe a certain feature in within the sentence link to the accomplishing task.
However gaining an overview is still simply done by looking at the margin and see the task-number there.
So I found myself doing both,
task:ABC-123[describing the task done inline]
while still generating an overviewtask::ABC-123[]
.This feel kind of double-work for the same task. What would improve the situation? I suggest to insert a simple option character to have both:
task::ABC-123[]
renders right ABC-123task::ABC-123[describing the task done inline]
renders right describing the task done inlinetask:ABC-123[]
renders inline ABC-123task:+ABC-123[describing the task done inline]
renders inline describing the task done inlinetask:+ABC-123[describing the task done inline]
renders inline describing the task done inline AND right ABC-123task:*ABC-123[describing the task done inline]
renders inline describing the task done inline AND right describing the task done inlineI'm open for other suggestions to avoid double-specification of tasks
The text was updated successfully, but these errors were encountered: