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

Templating #19

Open
gsumpster opened this issue Aug 22, 2017 · 4 comments
Open

Templating #19

gsumpster opened this issue Aug 22, 2017 · 4 comments

Comments

@gsumpster
Copy link

I think the ability to customize the task with variables pulled from JIRA would be very fitting w/ Omnifocus's configurable nature and would make this extension super powerful.

I'm interested in working on this, any thoughts @prometheas?

@prometheas
Copy link
Owner

Geez, talk about neglectful parenting… this is a wonderful idea, @gsumpster, and I'm rather ashamed it took me so long to even respond. Please accept my apology.

I'm deeply sorry that I failed to reply to this offer to help. I stopped using Chrome some years ago because privacy and power consumption, but Apple's WWDC 2020 announcement that Safari will be supporting Web Extensions this fall has rekindled my interest in this extension (which is why I'm here, doing a big of issues grooming).

In the event that the utility of this extension (by which I rather specifically mean its successor), I would be pleased to learn more about what you'd had in mind.

@gsumpster
Copy link
Author

Hey @prometheas, no worries! I've also stopped using Chrome for everything but development, definitely found Safari a lot less power hungry.

I was originally thinking that this would provide a pretty basic templating system to start with, so, if a user wanted they could write out a string like this: "{{TICKET_ID}} - {{TICKET_NAME}}", with more options for the body etc.

Can follow up if you want me to expand further!

@prometheas
Copy link
Owner

OK, this makes sense.

I'm still in discovery and work definition for the replacement extension, but since the markup delivered by Jira's "new" issue view have made DOM querying painfully more challenging, I'm "forced" to resort to REST API queries to fetch ticket information (which, frankly, exposes far more ticket information than was previously practical to scrape from the page, so there will be a richer set of template variable data to choose from).

Assuming you still use OmniFocus (or one of the other "major" macOS task managers… not to over-commit, here 😅 but that's part of why I'm starting form scratch), might you be willing to offer some product guidance around this, when the time comes in the weeks ahead?

@gsumpster
Copy link
Author

I do still use Omnifocus, though not currently using JIRA (current company uses Asana), but happy to look in!

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

No branches or pull requests

2 participants