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

hamster-bridge does nothing after start #13

Closed
sqozz opened this issue Feb 26, 2015 · 6 comments
Closed

hamster-bridge does nothing after start #13

sqozz opened this issue Feb 26, 2015 · 6 comments

Comments

@sqozz
Copy link

sqozz commented Feb 26, 2015

Hi all!
hamster-bridge seems like the perfekt tool i'm looking for. Unfortunately it does nothing after i start it.
Here is a log after starting hamster-bridge:

2015-02-26 12:03:18,375    INFO: Starting hamster bridge
2015-02-26 12:03:18,408    INFO: Activating listener: jira
2015-02-26 12:03:18,408    INFO: Registering <hamster_bridge.listeners.jira.JiraHamsterListener object at 0x7f8e5c141310>
2015-02-26 12:03:18,417    INFO: Starting new HTTPS connection (1): jira.domain.tld

I don't exactly know, how the bridge works but i whould except that hamster-bridge starts hamster after it gathered all informations from jira. For the sake of accuracy i also tried to start hamster first and then hamster-bridge and also the other way around - nothing.

Here is my (anonymized) hamster-bridge config:

[jira]
server_url = https://jira.domain.tld
username = foo
password = bar
auto_start = y
@sqozz
Copy link
Author

sqozz commented Feb 26, 2015

Seems, that the connection to jira works. It'd be nice, if the behavior of hamster-bridge is described somehow in the README or another document

@kraiz
Copy link
Owner

kraiz commented Feb 26, 2015

Yeah, i should add an explicit note about the supposed workflow in the readme.

You need to start hamster on your own. As soon as you stop a task, the bridge will search the title for a jira ticket name, if nothing found it searches in the tags, too. When it finds one, it will log the spent time to this ticket.

There's a feature request in #11 for writing the task description to the worklog comment. This will come in next version soon.

@kraiz
Copy link
Owner

kraiz commented Feb 26, 2015

I added some words in the README. Don't know if it's enough? What do you think?

@sqozz
Copy link
Author

sqozz commented Feb 26, 2015

Since i now found out how it works, your description seems pretty reasonable :)
Maybe you could add some words about the issue-finding from the hamster-bridge. My understanding is, that hamster-bridge tries to match the name (and? or? tags) to the first jira/redmine-issue it finds. What happens, if there is a matching tag and a matching name? Does hamster-bridge fillout multiple matching issues (e.g. hamstername is "issue1" and tag is "bugfix" - will hamster-bridge fillout the jira/redmine-issue "issue1 - fix something" or will it fill "issue 1337 - bugfix for xyz"?).

Since hamster-bridge does some automagic in the background, the user should know how that magic works to guarantee a stable and reasonable workflow.

BTW: used hamster-bridge today the whole time and it does it's job pretty well. So thanks for your efford in such a little but great tool 👍

@daroczig
Copy link

Yeah, for the first time, I was similarly not sure how and when hamster-bridge connects to JIRA, but after using it for a while, I figured out from the logs that it's connecting to JIRA when I stop the timer. Now the README is pretty clear and helpful.

I'd add an extra note, that you have to stop the timer if you want to log something, as if you do not click on "stop the timer" and simply change to a new task, then the time is not logged. At least here :)

But it's a really minor issue, hamster-bridge rocks.

@kraiz
Copy link
Owner

kraiz commented Feb 27, 2015

Glad to here your happy with it.

I added some more on the issue finding. Should be fine now.

@kraiz kraiz closed this as completed Feb 27, 2015
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

3 participants