HNHacker News
TopNewBestAskShowJobs

seanjregan

52 karma · joined September 25, 2014

submissionscomments
seanjregan··on Archiving repositories
From the Bitbucket Code Search Blog: Search indices built using traditional text indexers will usually return the usage result first because it contains a higher number of exact matches for your search term. In code bases where the same class or function is used many times, developers are often left trawling through page after page of usage results trying to hunt down the definition.

Bitbucket took a different approach: by boosting the definitions matching your search term, the result you want is likely to rank much higher (usually #1) in the search results. Bitbucket's algorithm boosts definitions for a wide range of type categories including classes, functions, enums, structs, and interfaces. Bitbucket prioritized building a code aware search scoped to team and user accounts over a global search functionality. This way, we hope to quickly give users the relevant results they want instead of the hassle of checking out a repo locally and searching using an IDE.

https://blog.bitbucket.org/2017/05/02/introducing-code-aware...

seanjregan··on Why GitHub Can't Host the Linux Kernel Community
I was waiting for someone to mention that. Free Aston Martins!!!!
seanjregan··on Ask HN: Passive income ideas for solo developers?
Niiiiice one. They don't all make money but there has been around $225-250m in revenues in the marketplace so someone is making money.
seanjregan··on Ask HN: How do you become productive in a new project as a senior developer?
Highlighting a table in Confluence, right clicking and turning each item into a JIRA ticket makes my life so much easier.

Similar with Bitbucket. Auto issue transitions means the devs don't have to muck around in JIRA as much. As soon as they start working on a branch (with one click in JIRA) the issue automatically transitions to the in progress column on the board, etc etc.

Reveal: I work for Atlassian and I work using Atlassian tools daily. Asana is a great tool but JIRA is built to help address the issues you are seeing. JIRA functions like a center of gravity to organize your work and many other tools (e.g. ~1000 integrations in the Marketplace connect into it.) We are working on some similar integrations for Trello and have shipped a few already.

seanjregan··on CodeStar – Quickly Develop, Build, and Deploy Applications on AWS
Hey Alexa- Can you fix these bugs for me now?
seanjregan··on Atlassian acquires Trello for $425M
Mr..Mrs. Cookie! I love Ice.... In my drinks but not for Bitbucket.

Bitbucket has released some pretty major stuff in just the last 6 months or so. Built in Pipelines are an example. We've got some other stuff coming soon and there is always more in the pipeline after that.

https://news.ycombinator.com/item?id=11759733

Bitbucket added support for large files and went a step beyond GitHub and Gitlab by adding file chunking to speed things up in a big way. Bitbucket added file previews to help those working with large files like gaming devs. Smart mirroring to helps remote devs work faster. I could go on but I don't want to spam this thread with a feature list.

There's a nice little post here with some things. https://blog.bitbucket.org/page/2/

Do you use Trello instead of JIRA? If so, awesome! It is a great product. We love it so much we spent around a full year of revenue to acquire them so rest assured that big of a bet isn't so we can just convert it into a lead gen tool. We believe Trello can be much bigger that than. (Alas, I can't comment on that right now as it is in deal closure period)

If you don't use JIRA LMK what you use and what you like better. I'm always up for listening to what we are doing well and can do better.

Caveat- if you can't tell I work on BB and JIRA. If you are in SF, I'll buy you a beer & a cookie for the answers, if not I'll just keep following this thread.

seanjregan··on Why I finally ditched Jira
That's why we highly value flexibility on JIRA. Forcing a terrible workflow on people is a sin. At the same time, we've always gotta help keep people from over complicating things.
seanjregan··on Why I finally ditched Jira
Some great upgrade news will be coming at Summit in October. You will like this.
seanjregan··on Why I finally ditched Jira
We are working hard on performance and have some major work underway to improve this.
seanjregan··on Why I finally ditched Jira
Sean from JIRA here. We are having our ShipIt hackathon today so lots of good stuff is going on in the office and there are some cool enhancements to JIRA being demo'd right now. I stepped out for a bit to address some of the comments in Ted's blog.

New tools pop up all the time and I understand the excitement that comes with finding a new one. Often these discoveries come with headlines like this that get the attention of a large audience (or target market) and then they deliver some promotion of the next big thing. That's fine, it is communities like this that propelled JIRA to where it is today and continue to power JIRA every day. Because the community of users powers JIRA, I wanted make sure we shared some of the detail that is relevant to Ted's post.

(apologies for the size of this but my hope is that it gives insight into some of the aspects of JIRA that you may not already use or know about)

Speed: We’ve got some major projects that will be coming online soon that will fundamentally accelerate the platform. This isn’t a small tweak, this is a core architectural improvement that will make a big difference across the board.

UI: Have you tried collapsible columns? This will let you minimize columns that you don’t care about so the columns you do care about are bigger. This allows you to see more of the ticket. Managing your backlog as the first column in a Kanban board is ok when there are only a few issues. But, as your backlog grows it’s hard to see many issues on the screen at one time. We’re going to let you split the areas of concern into two different screens with each one focused on the tasks at hand. The backlog is for backlog management and replenishment; the Kanban board for the engineering team to select and move the tasks through the workflow. This cuts down on noise and makes better use of your screen real estate. We are looking at a redesign for the issue view but more user research needs to be done.

Search: That’s good feedback…and something that we hear from customers who have larger and larger issue counts. I’d like to break your comment into two pieces, the speed piece, and the effective piece.

Regarding effective searches. We want to make sure everything in JIRA is searchable and JQL is super flexible. But, we also make sure it is easy to filter down to the specific information you need. In this instance, I’d advise doing the search the way that you have, and then using the status filter to separate out open issues.

In basic search, you can quickly toggle things on and off, for instance, issues that are resolved. This should give you the sorting functionality that you are looking for. Regarding speed. We are working hard on performance. You will see big improvements here as we keep focusing on performance over the next 6 months.

Organization: Epics are currently displayed as cards in Kanban and this works well for certain use-cases. However, you are correct that it makes it harder to identify what issues are associated with the epic and if used as a grouping mechanism, displaying the card on the board isn’t as useful. That’s why we will provide an option in the future to display Epics on the board, or use it as a way to group stories the way we already do it for Scrum.

To answer your broader question, here are a few more ways that help you organise your work in JIRA:

Kanplan: A great way to keep this work organized in JIRA Software is through the plan mode (aka backlog) which can be found when using scrum or the Kanplan feature in JSW Cloud. Trying to run a backlog and team task board together is distracting. Managing your backlog as the first column in a Kanban works great when there are only a few issues. But as your backlog grows it’s hard to see many issues on the screen at one time, the cards are large and the ones you care about are confined to ¼ of the page width or less, there’s so much scrolling. Splitting backlogs and tasks to two different screens with Kanplan helps- Backlog is for backlog management and replenishment and the Kanban board is for the team to select and move the tasks through the workflow. You can tab between Versions and Epics to see the progress of an Epic (e.g. number of issues, completed, unestimated, estimated, and even linked pages). Also, from this view you can mark the Epic as done and edit details. (http://blogs.atlassian.com/2016/03/kanban-backlog-jira-softw...)

Portfolio for JIRA: If you are interested in cross-team and cross-project visibility then a tool like Portfolio for JIRA would be a better solution. In about 2 minutes Portfolio automatically pulls together a view across all projects to show you the what-ifs for everything your teams are working on as you do resource planning in real time. With Portfolio for JIRA you can combine the work from multiple agile teams and roll them up into larger Initiatives. Think of Initiatives as higher-level business priorities or big projects potentially spanning multiple teams. When you look at Portfolio for JIRA you can see a visible roadmap, which can be viewed by Initiatives, Epics, and issues. And, if you want more levels, Portfolio for JIRA provides an unlimited hierarchy, so you can create levels above Initiatives and Epics to help bring organization to how your team works. Product-Level Planning- I’m not sure I fully understand what you are looking to do here. Happy to help if you want to explain more.(https://www.atlassian.com/software/jira/portfolio)

Config: JIRA Software was designed to be flexible and customizable and admins have set JIRA up to fit how their organization works. The issue here could be an administrative matter – schemes should be for global or project admins to change and it sounds like in this instance that too many people have access to these permissions. As teams grow it is important for teams to spend a little time dedicate time to the to thinking about how they want their own team to work. We could take the flexibility out but dev teams really appreciate being able to customize the way they work. In order to be a true agile tool, the setup needs to be flexible to meet the needs of many different teams. As a result, it is important to use permissions properly – this might mean that there is a council of stakeholders who go over customization asks, or there is an admin who is constantly working to improve and meet team needs.

Support: Based on the info we have from you the solution seems like it could be simple here: create a workflow transition from duplicate to resolved. In the current state, it looks like the workflow doesn’t have that. If that doesn’t do it, let’s work together with our support team to figure this out.

UX: Hell yes. We agree, killing UX friction is always important. We’ve shipped a few things recently that should help if you haven’t seen them.

Editable Fields: We’ve added more editable fields to tickets. Editing or updating details for an issue was not possible for most fields in the Agile detail view. Most users click through to the view issue page to edit an issue and then return to their board. This is slow, inefficient (several clicks and 2 full page loads) and context is lost during this roundtrip. (MEH!) Now you can edit right in the issued to that the user can stay in context and make quick, efficient edits. This saves time and eliminates loss of context. (Plus it means fewer tabs open in your browser.)

Collapsible Columns Make your screen real estate easier to manage.

Redesigning Agile Cards: We’ve redesigned the Agile cards so that in situations when column widths are small the cards can better communicate their content. This might happen when: Screen width is small, many columns exist or the sidebar and/or detail view is open.

To help fix that we worked on the following with the redesign:

-Improving the visual styling with a focus on ‘glanceable’ information -Creating a density option -Updated selection, hover & flag states -‘Days in column’ indicator -Improve stacking at small widths -Introduce sub-tasks attached to their parent in Kanban -Explore plan mode sub-tasks

-Sprint Permissions-We’ve improved sprint permissions. These can now be assigned to individuals, groups and roles and is decoupled and independent from Administer Projects permission. This enables simpler administration for group or role management e.g. ScrumMasters (often contractors) to work with teams successfully, and with minimized risk to the organization for unauthorized changes in the project. Repo Integraton: On top of JIRA UX improvements, we’ve done a lot to help take UX friction out of the interaction between the repo and issue tracker.

-Create Bitbucket branches from within JIRA Software- JIRA Software will automatically populate information for your new branch in Bitbucket and even suggest a branch name based off of the issue key. https://www.youtube.com/watch?v=K78Nk9kFdb0

-Transition issues in JIRA without leaving Bitbucket- Tickets in JIRA automatically transition when the dev merges, commits etc. This means the devs can stay in code but the project manager can see the activity and if there is a need to go back to and look at the issue and the code there are tied together automatically. https://www.youtube.com/watch?v=F_IIp4uenMw

-Give your entire team end-to-end traceability- Track the health and status of your next release from day one of development in JIRA Software’s Release Hub. Release Hub talks to Bitbucket to ensure that done code is really done and there are no inconsistencies or launch risks prior to launch day.https://www.youtube.com/watch?v=SRxklyR6fGw

There is always more we want to do and we take feedback seriously. Hopefully, this helps fill in some gaps and address some of the questions raised in this thread.

Cheers, Sean (Disclaimer: I work on JIRA)

seanjregan··on Why I finally ditched Jira
The more capabilities people have the opportunities they have to be great or be confused. It is a tough balance but generally speaking the flexibility of JIRA lets teams do some amazing things. We need to always we making sure it is harder for people to make mistakes but also need to make sure that our core users can have the flexibility they demand.
seanjregan··on Slack is down
ouch status page is down too
seanjregan··on Why Twitter’s Dying (And What You Can Learn from It)
Richelieu: "Give me six lines written by the most honest man and I will find in them something to hang him." How many tweets have you sent? Tweeted by Snowden today.

I think this sums it up. The web is a permanent record of the brilliant and stupid things that you have said and think while at the same time society has become very focused on responding to rather than ignoring the stupid things people say and think.

← PreviousPage 2 of 2