Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inline task macro links should optionally render task ID on page-margin #78

Open
torstenkraemer opened this issue Jun 23, 2017 · 3 comments

Comments

@torstenkraemer
Copy link

torstenkraemer commented Jun 23, 2017

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
  • proposal task:+ABC-123[describing the task done inline] renders inline describing the task done inline AND right ABC-123
  • proposal task:*ABC-123[describing the task done inline] renders inline describing the task done inline AND right describing the task done inline

I'm open for other suggestions to avoid double-specification of tasks

@kduske-n4
Copy link
Contributor

You don't need to mark tasks as done manually: #66
Ask @bsmith-n4 to set up a jenkins job that polls your repos for the task status.

@bsmith-n4
Copy link
Contributor

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.

See https://github.numberfour.eu/bsmith/task-status

@bsmith-n4
Copy link
Contributor

Regarding the feature request here, my vote goes to

proposal task:+ABC-123[describing the task done inline] renders inline describing the task done inline AND right ABC-123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants