As far as I can remember, when a ticket was moved between columns historically, it'd always default to be at the top of the list, unless you dragged it to a specific spot. That no longer seems to be the case, and instead tickets are added to the very bottom of the given column. Was this change intentional? Is there any chance we could introduce a setting to add back the original behavior?

Give HuBoard the ability to use new issue templates as per dear-github/dear-github#125

Official docs: https://help.github.com/articles/creating-an-issue-template-for-your-repository/
Announcement: https://github.com/blog/2111-issue-and-pull-request-templates

I currently use a linked repository to see all issues that are logged on all of my repos. This is fantastic for project management. However, I do not think that color coordinating each issue, based on the repo, is enough. Would it be possible to also put the repo name somewhere in the full details of the issue? Maybe in the right sidebar?

Steps to reproduce:

1. Create an issue from huboard.com with labels

Right now intercom is not enabled for the marketing materials.

We have a partial in app/views/shared/_analytics.html.erb where we define client-side Segment behavior on line 4. Need to figure out a way to make this work when current_user.id is null (pre login) so that we can still service anonymous users.

Related materials would be the segment.com documentation, also take a look at the segment intercom integration.

New error introduced by #208:

Message: undefined method `[]' for false:FalseClass

Backtrace:

/app/lib/hu_board/account_helpers.rb:33 subscription_canceled?
/app/lib/use_case/private_repo.rb:42 has_subscription?

Steps to reproduce:

1. Open huboard/huboard
2. Find issue #186
3. Notice the fullscreen breadcrumbs is not correct

Possible causes:

• Columns from linked repositories doesn't rely on the hardened array index but instead on the user entered label name index.
• Columns are based on a string comparison?

Expected results:

See picture above, give that both repositories have the same column names, we should treat them equally based on real index

When #214 was deployed there were two new app initialization errors:

Message: wrong number of arguments (1 for 0)

Backtrace:

/app/vendor/bundle/ruby/2.2.0/gems/faye-1.1.1/lib/faye/adapters/rack_adapter.rb:72 initialize
/app/vendor/bundle/ruby/2.2.0/gems/faye-1.1.1/lib/faye/adapters/rack_adapter.rb:72 new
/app/vendor/bundle/ruby/2.2.0/gems/faye-1.1.1/lib/faye/adapters/rack_adapter.rb:72 get_client
/app/vendor/bundle/ruby/2.2.0/gems/faye-1.1.1/lib/faye/adapters/rack_adapter.rb:80 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/etag.rb:24 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/head.rb:13 call
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/params_parser.rb:27 call
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:35 block in call
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:34 catch
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:34 call
/app/config/initializers/warden.rb:72 call
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/flash.rb:260 call

Message: Circular dependency detected while autoloading constant JobResolver

Backtrace:

/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:492 load_missing_constant
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:184 const_missing
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:526 load_missing_constant
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:184 const_missing
/app/app/controllers/application_controller.rb:44 queue_job
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:432 block in make_lambda
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:239 call
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:239 block in halting
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:506 call
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:506 block in call
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:506 each
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:506 call
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:92 __run_callbacks__
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:778 _run_process_action_callbacks
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/callbacks.rb:81 run_callbacks
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/abstract_controller/callbacks.rb:19 process_action
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal/rescue.rb:29 process_action
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal/instrumentation.rb:32 block in process_action
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:164 block in instrument
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/notifications/instrumenter.rb:20 instrument
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/notifications.rb:164 instrument
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal/instrumentation.rb:30 process_action
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal/params_wrapper.rb:250 process_action
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/abstract_controller/base.rb:137 process
/app/vendor/bundle/ruby/2.2.0/gems/actionview-4.2.4/lib/action_view/rendering.rb:30 process
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal.rb:196 dispatch
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal/rack_delegation.rb:13 dispatch
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_controller/metal.rb:237 block in action
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:76 call
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:76 dispatch
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:45 serve
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/journey/router.rb:43 block in serve
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/journey/router.rb:30 each
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/journey/router.rb:30 serve
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/routing/route_set.rb:821 call
/app/vendor/bundle/ruby/2.2.0/gems/ember-rails-assets-0.1.1/lib/ember/rails/assets/middleware.rb:8 call
/app/vendor/bundle/ruby/2.2.0/gems/pdfkit-0.6.2/lib/pdfkit/middleware.rb:17 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-attack-4.2.0/lib/rack/attack.rb:104 call
/app/vendor/bundle/ruby/2.2.0/gems/faye-1.1.1/lib/faye/adapters/rack_adapter.rb:81 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/etag.rb:24 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25 call
/app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/head.rb:13 call
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/params_parser.rb:27 call
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:35 block in call
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:34 catch
/app/vendor/bundle/ruby/2.2.0/gems/warden-1.2.3/lib/warden/manager.rb:34 call
/app/config/initializers/warden.rb:72 call
/app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/flash.rb:260 call

remote: -----> Preparing app for Rails asset pipeline
remote:        Running: rake assets:precompile
remote:        rake aborted!
remote:        ArgumentError: Missing required arguments: aws_access_key_id, aws_secret_access_key

Might consider either making those keys optional, and feature-flag the related functionality accordingly, or adding a bit to the deployment documention on the use and recommended IAM policy for those keys. Happy to pursue and contribute one or the other.

Example can be found on skipping_stones_repo, the skipping.stones repository has slightly different column lablels

There is still a case when a properly formed PUT can bounce where the body_html and body_text are ok but the body field is blank

Under certain circumstances real time events can be lost causing boards to fall out if sync with GitHub.

One obvious reproduction of this is when a browser is closed and reopened later, a saved HuBoard tab will reopen to the last know state, but the events required to sync up are long gone - this can be chaotic for users during morning stand ups and meetings.

I suspect (but have not confirmed) this can also happen when a tab is either left unattended for long periods of time, or a system has been left in sleep mode. One of our users reports:

There is something seriously wrong with Huboard's synching with GitHub. Even when I'm actively using Huboard it does not resynch my browser session with GitHub. I'm constantly finding myself in situations where my guys are asking me to look at a bug and when I query for it, it doesn't show up in Huboard. I have to do a full refresh before I will find it. Really frustrating.

Also Relates to missing Events: huboard/huboard#598
Closes huboard/huboard#214

Task List:

• Implement Sticky Toasts, and Stateful Progress Toasts
• After a period of inactivity, run a diff on the browser on focus to determine if any events have been missed
  • Track the last X number of events processed
  • If events are missing, and not past the X threshold, fetch the missed events and play them on the client
  • Disable board use during any syncing activity
  • If events are missing and are past X threshold, prompt for page refresh

As per https://app.raygun.io/dashboard/7lc2yw/errors/726459500

I am getting the following output. The line dalli.get(key) is highlighted red. Any ideas?:

cache.with do |dalli|
logger.debug("Cache read: #{key}")
dalli.get(key)
end
end

We go into more detail as to why on our blog, but what you need to know now is that as of 1 December 2015 we are not accepting any new accounts, project upgrades, or font purchases. Fonts will stop being served on 1 December 2016.

We hope this will give you plenty of time to find an alternative source for your webfonts. To help with this we’ve put together a comprehensive migration chart showing where you can get webfont licenses for each of our foundry partners.

I'm not sure it's the right place to ask for features, but ...

In Milestones view, it would be great to have the possibility to filter on defined columns .

In my project, I have a Idea/Discussion column and a Backlog column, and I want to assign milestones from Backlog columns only right in the Milestones view.

Today, I have to do it in the Task view, but it's not really appropriate because it requires to open all issues from backlog column, and set the milestone manually for each of them. With the columns filter in Milestones view, it would be possible to perform this more quickly with drag&drop.

Thanks for this great tool !

Use case:

1. Have a project selected as a filter and a label selected as a filter.
2. Scrolled way down to an obscure ticket.
3. Click on a link in the ticket. You now go to the new page, but on back all of the filter settings and position information is lost.

Seems like there are a couple of solutions:

1. Always link off the site for external links (any links)
2. remember in the URL the filter settings to reload the page properly. Also would handle the link sharing use case.

Possible causes:

• OAuth token is mysteriously getting revoked by GitHub
• We have some weird cookie bug that I'm too noob to understand about
• Other???

Possible fixes:

• Sliding window expiration on our cookies
• Talk to the gitter guys, they don't seem to every have this issue
• user multiple OAuth applications (one for public one for private)

It looks like portions of 5496c46 should be reverted/updated to reflect it's current home.

@seanlinsley suggests we should upgrade for security fixes. I agree.

Rails version needs to be bumped both in the root Gemfile and in saas.gemspec.

Steps to reproduce:

1. open up a HuBoard
2. click a card to fullscreen the issue
3. scroll down to the comment box and try to @mention a user

Expect:

An autocomplete list to show up with autoselection

[Should pass]

Steps to reproduce:

1. Scroll half way down the page
2. open up a HuBoard
3. click a card to fullscreen the issue
4. scroll down to the comment box and try to @mention a user

Expect:

An autocomplete list to show up with autoselection

[Should :fail:]

Currently the HipChat Integration is hard-coded, this should be an optional string to allow on-prem hipchat integrations to work as well.

Steps to reproduce:

1. Plug in a mouse
2. Open a modal
3. Fail...

First of all, let me say you guys have done an awesome job with huboard. Probably the biggest pain point for me is that i can't create an issue and assign it to a column at the same time. Maybe I'm overlooking something about why this might not be desirable. Just to make a case for it though, our default column is Backlog. However, when creating a new issue, we often want to put it directly into the second column "Todo". Is this anywhere on your roadmap?

https://devcenter.heroku.com/articles/github-integration-review-apps

Build up analytic goal tracking for HuBoard

• Enterprise Contact/Trial submit
• Enterprise Login to Dashboard
• shared/analytics in every view
  • /login #194
  • Errors?
• Login actions
  • /login/(public|private) ✓ #232
  • /login/(public|private)/authorized ✓ #232
• Basic account actions
  • /settings/{owner}/trial when email prompt is shown ✓
  • /settings/{owner}/trialing when email prompt is submitted ✓ #207
  • /settings/{owner}/expired when an expired trial board is accessed ✓ #208
  • /settings/{owner}/canceled when a cancelled account board is accessed ✓ #208
• Account reactivation (requirement of huboard/huboard#635)
  • /settings/{owner}/reactivate when a long-expired/cancelled board is accessed
  • /settings/{owner}/reactivating when a reactivation trial is started
• Board actions
  • /{owner}/{repo}/board/create when we offer to create HB labels ✓
  • /{owner}/{repo}/board/creating when we are asked to create HB labels ✓ #233
• /settings/profile actions
  • /settings/{owner}/upgrade when Upgrade is clicked (popping Stripe)
  • /settings/{owner}/upgrading when Stripe is successfully submitted (/settings/charge/dahlbyk) ✓ #230
  • /settings/{owner}/canceling when an account is cancelled ✓ #230
  • What else?

Whenever a user attempts to navigate to a organization at settings/profile that they are not a part of, they get thrown a white screen of death. This should probably show them a message stating that they are not a part of the organization / do not have permission to edit, and perhaps send them a link back to their main profile page.

Closed by #158

This appears to be a partially implemented feature:

Please advise, thanks. My team and I are evaluating HuBoard, so it's good to know what to expect when we see things like this.

Session Loss no longer triggers as ghee is sending 500's back instead of 404's

I really enjoy using emojis in my github commit messages but emojis don't render properly on huboard.

Disable it if there is an existing column structure that is incompatible.

Let this twitter user know when we have fixed it.

https://github.com/huboard/huboard-web/blob/master/ember-app/app/templates/components/settings/hb-link.hbs#L40-L51

I work with a team of about 10 people, and often we need someone to review an issue before it can get moved to "done". Currently, we just place it in review and "@" mention the person who needs to review that item, however, with a growing team that is managing much larger projects, this is becoming difficult to manage.

We are looking for a way to add team members to an issue that are responsible for reviewing the work done in that issue. Some key information that would be helpful is if the reviewer has opened the issue since it was placed in review, and maybe an indicator that the user approves this work. It would also be helpful if these reviewers received a notification email when an issue is moved into "Review". It is important that the review is tied to a user, and not just a free floating feature. It is also important that more than one reviewer can be added to an issue.

Good enough:

• Change the copy of the "Sign in" button to an icon button with the octocat and "Sign in with GitHub" - @discorick
• /login Simplify the two step process with just [Sign in with GitHub] - @discorick
• /login Add (Green icon) Your email to the permissions asked for - @discorick
• "Sign in with github button" Change it's default behavior to "public" scope + email - @discorick
• Force a re-auth for all new "login" clicks
• Move public vs private to separate OAuth applications - @rauhryan
• Store credentials in couchdb (must be encrypted)
• Change copy on pricing page to say we store tokens with XYZ encryption and never look at your data without your expressed permission
• Ensure that email that is collected is making it into intercom [#1 criteria for acceptance]
• Sense public auth only on the dashboard and provide an upgrade option - @discorick

Better:

• Skip /login all together and default to "Email scope"
• [DASHBOARD] If we only have the "email" scope, the landing page should be a "Welcome" here's how you get started similar to what [/login] does today.
• [DASHBOARD] If we know they only have Public access, have an option to upgrade to private ("Not seeing your private repositories? [Upgrade access] [?]"

Since #217 was deployed we're getting a few of these:

Message: undefined method `[]' for nil:NilClass

Backtrace:

/app/app/jobs/issue_event_job.rb:29 block in build_meta
/app/app/jobs/issue_event_job.rb:29 call
/app/app/jobs/issue_event_job.rb:29 build_meta
/app/app/jobs/issue_event_job.rb:35 guard_against_double_events

Relevant line:

The login jobs introduced by #182 are failing periodically with:

no implicit conversion of String into Integer

/app/vendor/engines/saas/app/jobs/login_private_job.rb:5 []
/app/vendor/engines/saas/app/jobs/login_private_job.rb:5 block in perform
/app/vendor/engines/saas/app/jobs/login_private_job.rb:5 each
/app/vendor/engines/saas/app/jobs/login_private_job.rb:5 detect
/app/vendor/engines/saas/app/jobs/login_private_job.rb:5 perform

The failing users show a Not Found payload instead of the expected array -

          emails: {
            "message": "Not Found",
            "documentation_url": "https://developer.github.com/v3"
          }

Checklists

• are disabled

for collaborators if you are not the creator of the comment

http://stackoverflow.com/questions/12480497/why-am-i-getting-error-for-apple-touch-icon-precomposed-png

We have implemented variations on this theme in several places: #124 #198 #199 #202. None of them seem to be working as expected in Firefox:

https://huboard.com/dotnet/roslyn columns aren't equal width, and on https://huboard.com/dotnet/roslyn#/issues/56883993:

So two things:

1. We need to stop using word-break: break-all altogether. word-break: break-word seems fine but is Chrome-specific.
2. Firefox does support word-wrap: break-word (an old property since renamed to overflow-wrap - we should probably include both), but there are caveats to it working as we need it to within display: flex: https://bugzilla.mozilla.org/show_bug.cgi?id=1136818.

We need a standard pattern for this to be implemented everywhere we render user-generated text.

If you change your GitHub username and attempt to login to HuBoard it throws a 500. A cookie clear is required to regain access to HuBoard

When dragging cards with either have 0 order, or to columns with cards with 0 order, sorting breaks and cards do not retain their expected position.