Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Search the Community

Showing results for tags 'invision'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Organization
  • Leadership
  • Requirements
  • Design
    • User Experience
    • User Interface
  • Development
    • Frontend
  • Quality & Security
  • Deployment & Network
  • Atlassian
    • Jira
    • Confluence
    • Bitbucket
  • Wordpress
  • E-commerce

Categories

  • Project Manager
  • Process & Method Specialist

Calendars

  • Community Calendar
  • Organization Events
  • Leadership Events
  • Design Events
  • Development Events
  • Deployments Events
  • Requirement Events
  • Quality Events
  • Atlassian Events
  • Wordpress Events
  • Atlassian AUG Stockholm's Events

Forums

  • General Area
    • General Area
  • Areas of interest
    • Organization
    • Leadership
    • Design
    • Development
    • Deployment
    • Requirements
    • Quality
  • Special Areas
    • Atlassian
    • Wordpress
  • Atlassian AUG Stockholm's Diskussioner

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 1 result

  1. Invision is a popular tool for visual designers and UX designers, but it is usually a pain to transfer the information over to Jira. With Invision for Jira that becomes less problematic since you can embed an inline prototype directly into a Jira issue that also include the inspect function that makes life easier for the developers. While this is very nice, it really is just a fancy way to link people to Invision because the links will take you to Invision and you get the same issue with making sure everyone have a login and understand the way Invision works. This does not solve the actual problem to bring in the information the designers need into the documentation, it just add a more convenient way to direct the users to Invision. So this leaves the designs in Invision, which is not a good place to keep designs once they are agreed upon since you need to ensure the designs are not continuously improved as that cause issues with requirements. This can be solved by transferring projects to a another, controlled Invision instance, but that is messy and prone to confusion and mistakes. What I would like to have is a way to embed this directly into Confluence where it can be version handled and controlled from a requirements perspective. The concept is amazing, but the solution right now is not enough for a good way to bring in design in a controlled way as a requirement into Jira unfortunately.
here
×