I imagine that you are trying to handle the ability to quickly create multiple issues in a row; however, there should be an option to create a single issue and dismiss the modal in a single click. Typically, I would expect this to be handled through separate buttons — "Create" next to "Create and Add Another" or something. In addition, and especially for the "Create and Add Another" path, the modal needs a close and/or cancel button. In my experience, hitting escape or clicking on the overlay is not the most noticeable option for the average user.

If you have 100 repos to pick from, the dropdown (in the settings UI, or list in the onboarding UI) is borderline unusable. The repos aren't sorted in any obvious order, and there's no search.

Consider sorting alphabetically (if possible), and adding a search-as-you-type box (e.g. chosen.js).

Really long issue titles (like the ones Airbrake generates for us) break the layout — pushing the milestone table outside the browser window. Some responsive and/or more aggressive title truncation would help with this.

I have a milestone that has 27 issues in it. So, there are issues "above the fold" with a white background and some "below the fold" with background color of #fdf9f6.

When I drag an issue from the white section to the #fdf9f6 section to re-order it, the issue snaps back to its original position.

When adding someone as an organization member, I expected that an invitation email would be sent to them.

Is it possible to switch between milestone-based / assignee-based interface after a project has been created?

I'm talking about the "prioritization" setting that I've chosen when creating my project.

Current

When ownership is (manually) transferred, the previous owner will still see the "Update your payment information before your trial expires." box, even if a payment method has been added.

Expected

If I'm not an owner, I shouldn't know anything about payments.

Screencap

It would be very helpful, especially if things get out of sync, to have the ability to delete milestones in the Codetree interface.

When organizing multiple projects, we need to be able to easily assign milestones.

It feels right to be able to drag between milestones like this:

If the milestone doesn't exist for that project, creating it would be fine.

Creating an issue returned an error, and it looks like the error div isn't there for the particular error, so the JS pooped out.

Right now the issue filter system offers a few manipulable options, as shown here:

However, it's (critically, I'd say) important that the "assigned to" part is a multi-filter, too, so that we can search for things like

"Showing [open issues] [assigned to or @-mentioning] [Pomax] labeled with [p1]"

As a codetree user, I may need to change my organization owner to someone else because they are the one with the credit card.

Please allow me to change org owner to another user. In the meantime I'll be sitting here with your money in my hand. Thanks!

For projects with a large number of milestones, the main issue view can be slow and unwieldy.

This should vastly improve the Webmaker dashboard @simonwex

Would be nice to see the following:

• Ability to close the issue from the app
• Ability to view the body text of the issue in the app

It would be incredibly useful to be able to sort issues in a given milestone by different criteria including Assignee, #/Creation Date, and Recently Updated. Ideally, it would be nice to be able to simply click on the table header to change the sort.

Requested by @simonwex.

Right now, users given too many decisions to make when filing an issue. (Actually, we need to hide a bunch of options in the new issue modal for users who do not have privileged access to the repository, since GH will ignore these when not allowed).

• Need a clear convention for triaging issues
• Possibly a "move" operation (i.e. closing the original issue, opening a new issue in the desired repo, and dropping a reference back to the original)

I just imported an admittedly-huge number of repos (All of Mozilla Foundation's) and it's stuck on this screen:

Project id "KqyK"

It's been running for 10 minutes. I could see this being expected behaviour. If that's the case, resolution of this issue would be a more granular status update on-page.

FWIW, even the word ("shortcut") confused me.

My main difficulty though was with figuring out how they worked. The first time I used it, the UX made me think that I needed to create the shortcut and name it first, then set all of the filters. I created a couple of shortcuts in a row that were simply duplicates of the Issues view. At the very least, some explanation text would be helpful.

Would be nice to be able to sort and/or reorganize Projects, as you can with Milestones and Shortcuts, and have the order reflected in the Codetree navbar dropdown.

Requested by @awaxman11. Would prefer label-based storage (e.g. "size-1", "size-8").

I'm leaning toward comment/body-based storage, like this: points:5. Another option is title-based, like this: Assigning agile points [5], where [5] indicates point value.

Notify https://secure.helpscout.net/conversation/64951821/67/

Hi,
I'd love it if you could add a "Repository" column to the issue list, so that one can see from which repo an issue is coming from at a glance.

Maybe you could also make the visibility of certain columns optional for people who don't need to see them. (This could be related to #7 )

So that you don't have to change the repo every time you create an issue.

There's a repo that I have on my list of repositories on GitHub but cannot add to a Codetree project.
It's a repo that I've been invited to with a collaborator access permission.

Could you make this kind of repository available in Codetree too?

First of all, congrats on the Custom Stages release!

Second, now that I've had a chance to see how you guys implemented it, I have an additional request. It would be helpful if type were a criteria for the custom stages. For example, my team creates (or converts existing issues to) pull requests when something reaches the review stage. So, it is a bit redundant to have to also move it to the custom stage and/or add a label to it. If I could specify something like "is a pull request OR is labelled 'review'" for a custom stage, that would be most excellent!

So that I don't have to delete them and recreate them.

I created new milestones in Github, but after 10 or 15 minutes they never showed up in Codetree. But, creating them in Codetree did create new milestones in Github.

Can we get some clarity on how this is intended to work?

As part of this, how do we go about editing a milestone name so that it appears synced in both Github and Codetree?

Another corollary would be: what can we expect for syncing between Github and Codetree? How often does it happen?

There's probably 10 feature requests that could come out of this issue depending on the answers :-)

Excited to see we can add columns to the task board! Thanks!

There seems to be a bug that has the column show up after my "Done" column though.

There doesn't seem to be a way to delete a shortcut once it's created.

I moved one of my issues to a different, newly created milestone, and the change is not being propagated back to the app. New issues for that milestone have showed up, but not the one that was moved.

When my issues/milestones get out of sync with the GitHub Issues Truthiness™, I'd like to be able to force Codetree to re-sync now as opposed to sometime.

Or at the least, so visibility into that re-syncing schedule / progress would be swell.

/cc @andacturkmen @lightcap

We've invited our customer support team to our github org and instructed them on how to create issues. We'd love for them to be able to use the CodeTree UI, but in order to do so, they need to be able to attach screenshots and other assets (eps, ai, svg, pdf).

We had a milestone named: "v1.4 Feed".
We changed it to "Public Feed".

New issues created in this milestone show the correct name ("Public Feed").
Issues created in this milestone before the name change retain the old/wrong name ("v1.4 Feed").

Projects are strictly private at present time. Public projects are a must for OSS. Similar to assigning, labelling, milestone assignment, etc., prioritization will be limited to those with privileged access to the project. Non-privileged users will be able to browse issues, create new ones, and create their own shortcuts.

/cc @simonwex

I love the new task board ❤️

In addition to organizing issues by Backlog, To Do, In Progress, and Done, it'd be great to be able to customize the columns. One way to do this would be to have them associated with GitHub labels. For example, in the case below a Backlog label would be applied to the issues in the left hand column, and when moved to the To Do column the Backlog label would be removed and a To Do label would be added.

For a large number of projects being imported, it appears to get stuck. It does finish eventually, but would be good to give the user some insight into progress. -- Otherwise they file silly issues like #1

Linking a Codetree organization to a Github team might provide a low-effort mechanism for team management.

https://developer.github.com/v3/orgs/teams/

Requested by @simonwex.

• A report/filter to show issues that currently need the user's input, using a tagging convention (a la "fixes #xxx")
• More intelligent notifications?

I tried to click on an assignee like you can in the list view.

Always seeing two avatars (one assignee, one creator) adds some serious cognitive processing cost. =)

At least to me, assignee is always relevant, creator rarely so.

I really wish there were a way for me to hide the creator — it's really tripping me up! =P

There is one closed issue (#3) in my account that is showing up on the open issues tab. This issue has been closed for a few weeks now, so it should have been synced (I think).

When I'm already logged in and I visit codetree.com, I always just click on "View my dashboard". Please save me a click and redirect me to same place as that link instead of showing me this page.

Small thing, but it's strange glancing through the Done issue on your task board and seeing the "in progress" label still attached to them.

I've created a new org and repos. I'd like to be able to add them to an existing codetree org. How do I refresh the list?

I would like to be able to specify a Shortcut as "global" so that every member of the organization can see it. We started testing out Codetree for review during bug meetings and, depending on who leads the meeting, we can't rely on the same shortcuts for review.

I have a milestone that shows as 97% complete with one issue open, but I don't see any open issues in the milestone.

Clicking on the milestone itself also reports "Hooray! No issues to show here". Seems like something out of sync.

The default set of milestones for my repo seem to include all of the ones that are closed on GitHub.

I can close them manually for now, but can you not detect that on import?