An Invision & JIRA combination. It's like they can see into my nightmares.
I try to stay out of Jira as much as possible.
Looks promising. Invision takes one more step past Adobe.
I got really excited about this! But it's only available for Jira Cloud accounts ATM.
Stephen, really excited about this release! It's seriously going to change how we work at OpenTable.
While prototypes are valuable, seeing all the screens laid out is also great. I currently deliver one big page with all the screens and logic to Jira. I'd love something like this automatically generated by Invision.
Beautiful- so glad Brooks! Love the suggestions please keep it coming and hit me up personally at stephen[at]invisionapp.com if theres anything else that comes to mind that we can do here.
interesting. this makes a compelling case for multiple, small-scope prototypes rather than "big picture" type stuff. but i'm not sure many people work that way right now? (i don't)
Jim- we kept the scope on this one purposefully contained at launch to a few key value props (link a project, view a project, extract value via Inspect). Looking to continue to evolve this so that it works for both small-scope and big picture type linking. I think your observation here are astute.
One of the future features we're actively working on is ability to extract just a subset of a project/prototype to associate with an issue. I suspect this will address the big picture case described above where you have one big project that would associate to multiple issues. Appreciate the feedback- so, so helpful in equipping us with what we need to push this one further!
that would be incredibly useful! thanks for clearing that up.
That's also the way I work. Linking a project to a story could be done before via a shared link, so I don't see the the value prop is here - yet. Looking forward to being able to link an issue to a single screen and/or series of screens, hopefully in the next release!
Plenty of us who work on enterprise products supporting multiple teams do.
Personally, what i've found is that one big monolithic prototype doesn't work for those sorts of projects. Our prototypes are so large, that our developers get lost and don't know which screen they should be looking at.
I'm with you on this. I used to try design to the big picture, but it doesn't work with agile methodologies. I have started to work smaller scale and week to week to align more with my developers.
agreed, from a development point of view. but our product managers are always looking for complete prototypes to both see the big picture and also to demo to stakeholders/clients.
Actually we do it quite a lot (enterprise env).
In the beginning of the project we create one prototype for the "big picture" and containing only the core functionality or two. Not every detail. Once that is evaluated and confirmed we go into the "delivery" phase. There I create a prototype just for the specific user story/functionality from sprint to sprint. I also have a rule of thumb that it can contain max 4 screens. Keep it simple.
This makes communication and alignment much easier. Funny enough is that our current work flow includes me pasting InVision links to Jira as a comment when I finish a task :) So this plugin seems like made for us!
I'm very curious about the Inspect part, though. If that works as expected it would definitely close the loop. Currently we are still relaying heavily on Zeplin. So a lot of Jira issues get in addition to an InVision link also a Zeplin link. Which get's tricky when people start commenting all around...
This might sound like a silly question, but what do your prototype names look like, especially if spanning multiple projects.
I have considered multiple prototypes for a single project in the past, but I think I was afraid of becoming disjointed and disorganized. Seeing you bring it up has me inspired O_O.
For what its worth we see several different types of organization on the InVision side. The three main models I see most (in no particular order):
- One unified prototype with many screens and singular share
- One unified prototype divided using sections, with sharelinks created per section and distributed
- Separate prototypes for one project based around section
There's not a right/wrong way to do it but I would say that based on the scope/size of your project, the best approach varies IMHO. Example: if I'm jetting over 40+ screens I'm probably going to take one of the latter two options above.
Interesting. We fall into the second model and we're at a point where it feels like the third sounds cool, but might create too much management. But it has me thinking that someday it would be interesting to see multiple prototypes live under a Project and be tagged in such a way that prototypes could be easily distinguished by Epic.
Stephen highlighted the right three categories. And we went through all of them :) Currently in the second and third category.
But naming is indeed tricky. I did change it quite a bit through the course of the project. Currently our naming convection is kinda like this:
Not perfect, but the team got to understand it and we find things quite fast.
One thing to note- we're working on a better solution for what you describe here which you'll see kicking out soonish. Can't give exact details just yet but we totally agree with the use case you describe and are cranking on it. Thanks again for the feedback! :)
Good to hear this Kristjan- thats what we observed as well when sitting with customers and users. If you have an enterprise account you can give Inspect a go now, all other accounts will get access in the very near future. Thought is- for devs/engineers interacting with InVision, we want to make it as easy as possible to access just the value they find most value. In JIRA thats ability to view prototype (and in future individual screens or subsets of prototypes) and extraction of meaningful dev resources such as assets, css, color values, spacing, measurements, etc (which is where Inspect comes in).
Yes, discovered the Jira plugin for Invision and we were quite excited about it - until we found out that it's only for the cloud version. And we are old-school with an on-prem :) So I guess we have to wait a little but definitely looking forward to it!
Love that Inspect bundles into the JIRA, but I don't use Invision prototypes on most of my projects. Anyway to just use Inspect?
Taylor- totally possible. As long as you upload the working file to InVision, you can trigger Inspect. Same would be true for JIRA integration- link the project then click through to Inspect (even if you don't have a prototype wired up, it'd still push through to Inspect via artboard detection and give you access).