Either via gerrit integration or pull requests style.45 votes
The code review has been now released. Check http://blog.deveo.com/deveo-3-0-0-released/
Currently only webdav support clients are the only way to upload files to webdav repositories.
I would like to see a feature that would allow me to drag & drop/html form to upload files to webdav (e.g. google drive or dropbox).
I don't mean that this feature should support 9TB binary files upload but simple documents (pdf, docx), images etc.32 votes
Issues on a board with states, with drag/drop for moving them. Preferably adding a new state/workflow by reordering state columns.27 votes
The trello-board was done in deveo 3.11. Check out the release blog post for more information: http://blog.deveo.com/whats-new-in-deveo-3-11/
The drag & drop is being implemented at the moment, and will be released soon.
It would be very interesting and useful to have some issue tracking system in the website. Something to track bugs, share issues or post new things that should be implemented in the code.25 votes
We have released the first version of the Issue tracking feature together with our new UI. Please check the blog announcement here: https://deveo.com/blog/2014/08/18/the-brand-new-deveo-now-in-beta/
Code review tool needs ability to see whole file side by side while reviewing. Now you can see only lines which area inside patch.
Reviewing code would be easier if you could do review by seeing whole file side by side. For example now you only see little part of some function when committer have done some oneline chage to that function. It's hard say if the change is good.14 votes
This feature was delivered as part of Helix TeamHub 2017.2: https://www.perforce.com/products/helix-teamhub/release-notes#helixteamhub20172
As far as I know it is currently impossible to reorder issues (in a column) on the kanban board.
It would be very useful to have one or both of:
1. Sorting issues by priority. This would require the priorities to have a defined order.
2. Manually setting the order by dragging and dropping issues in a column.11 votes
The arbitrary ordering is possible in Deveo 3.19 in the Kanban board view. The sorting by priority is possible in the list view. We are not going to implement both in both views as it would be ambiguous. Read more about the 3.19 release from our blog at http://blog.deveo.com/whats-new-in-deveo-3-19/ or release notes at https://deveo.com/releases/3.19.0/
Instead of a .sh installer, you could provide .rpm installers for Deveo On-premises. This would likely reduce package conflicts and make Deveo easier to install on company infrastructure.10 votes
Deveo is now shipped as native OS packages, such as RPM and Deb. Log in to your Customer Portal, download the package for your operating system and follow the instructions at http://support.deveo.com/knowledgebase/articles/322522-installing-deveo-on-premises
There should be an option to squash merge the changes at the end of a pull request. This results in a single commit instead of the individual commits plus a merge commit. This is preferred by some development teams to keep the history clear and simple. When this option is available, the user should be able to freely edit the commit message. The ability to do a squash merge should be a configurable option on the target branch, such that users don't accidentally squash to branches, where we don't want it.7 votes
The current hipchat hook uses hipchat API v1, which does not allow for "room owners" to generate tokens with which to post notifications. An administrator must generate a dedicated token.
If I understood correctly, APIv2 allows room-specific tokens to be used.5 votes
Currently, merging from deveo does a fast-forward merge, if applicable.
This causes Jenkins to not trigger a build (https://issues.jenkins-ci.org/browse/JENKINS-17411) from such a merge to master, if the branch was built already.
This issue seems to divide opinions, so please make it a repo-specific setting to do merges fast-forward or merge-commit.5 votes
I personally haven't created an RSA key in years. All of my systems (and other cloud services) support Ed25519.4 votes
This has been implemented in Deveo 3.12. http://blog.deveo.com/whats-new-in-deveo-3-12/
Do let us know of any additional requirements or keys you wish to be supported.
Currently repo hooks using the webhook service type can only subscribe to "push" events. These hooks however do not fire if a new tag is pushed to a repo, only when new commits are added. I would like to be able to receive tag creation events in my webhook, so that I could trigger CI events for them downstream. This would enable e.g. automatic releases of tagged versions while supporting developer workflows where tags are pushed after the commits.4 votes
We have released this functionality as part of Deveo 3.20. Deveo now supports triggering webhooks on Git repositories for commit, branch and tag related events.
You can configure the triggers from the hooks view as briefly covered in our release blog post:
Please refer to our User’s Guide to see an example of the payloads for each trigger:
The ability to search a repository from the webui would be very useful. I have a few senior developers who will assist our fresh staff on issues via mobile or computer without a git client. Our prior git hosting had a repository search functionality baked into the webui which allowed to to more easily provide feedback on specific code issues.3 votes
Hey, how about a fork functionality? Would it not be best done inside Deveo, so that Deveo would know.2 votes
Forking has been implemented in Deveo 3.16. Read more from our blog about the newest release: blog.deveo.com/whats-new-in-deveo-3-16/
On GitHub and BitBucket, repository URLs end in .git, e.g. foo.git for a repository called foo. GitHub also accepts (and presumably redirects) if the user tries to access with just ...foo (BitBucket doesn't). The Git convention is for bare repositories' URLs to end in .git, but accepting both URLs seems the best solution.
Currently, there's no way for a user to pick one convention, either foo or foo.git, and use it consistently across all three services. (A workaround exists: use .git, and name the project itself "foo.git" in Deveo - obviously not ideal.)1 vote
This was implemented as part of Helix TeamHub 2017.1. You should be now able to use both the repository URL found from the web UI as well as the same url appended with .git suffix.
Already mentioned in the original code review feature request: http://support.deveo.com/forums/169467-general/suggestions/4889530-code-review1 vote
Released in Deveo 3.5.0 https://deveo.com/releases/3.5.0
Any newlines in git commits sent to the hipchat hook are ignored, hurting the readability of the notification message.1 vote
This is implemented in Deveo v.3.1.0, thanks for pointing it out.
This is a bug, currently you cannot navigate into a directory if the name contains a hash.1 vote
In the code review it would be nice to be able to fold the diffs of single files.
E.g. when looking for bugs, I know it won't be in Readme.txt, so I want to hide the diff of that one.1 vote
Folding the diffs for single files has been implemented.
When you add label with . the UI doesn't show that it's illegal character. Although why it should be?
Steps to reproduce:
1. Create milestone
2. Create issue
3. Add label to issue
4. Add label with . in label e.g. MKOv.12
5. Add label to iissue
6. Go to issues
7. Can't filter with new labels after label with .
9. Labels are gone1 vote
support for dots in label names was added in https://www.perforce.com/products/helix-teamhub/release-notes#deveo3180 Deveo 3.18.
- Don't see your idea?