Skip to content

Settings and activity

9 results found

  1. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Axel Hermes commented  · 

    We have also the request in our team to limit screens shown in a link (not just for Jira) to a specific range of screens.
    Reason is that it is sometimes hard for developers or stakeholders to understand where the boundaries of things to look at is.
    Currently it is in discussion if we need to separate files to create mini-prototypes focussed on a specific ticket. Which has other disadvantages.

    Axel Hermes supported this idea  · 
  2. 1,540 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Axel Hermes commented  · 

    This is a major pain point! How can I handle hand-over to an other designer during vacation or when somebody leaves a team? I cannot share my Adobe ID account because designers in the team are working in different companies.

    We as the users should have the right to decide who is / are the owner(s) of a document with the according rights.

    Even if having multiple owners would be a problem we need at least the possibility to hand over ownership of a document to somebody else.

    Especially if the file is used as Pattern Library for other documents! Building Design Systems is team work.

    Axel Hermes supported this idea  · 
  3. 166 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Axel Hermes supported this idea  · 
  4. 128 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Axel Hermes supported this idea  · 
  5. 2,509 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Axel Hermes commented  · 

    Please also make data population of components in a repeating grid possible.

  6. 101 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Axel Hermes commented  · 

    Populating is currently only possible if the elements are not a component.

    For example you have a card module with image, title and a paraphrase as a component, because you want to to use in various places. If you then drag a text on the title element of the card, all repeated cards get the same title and not the different titles from the txt.file. Plug-ins refuse to populate any data.

    This applies also for Plug-ins like Data Populate, Repetor or Google Sheets. For Data Populate it is also not working it the card is a group.

    You need to break a component apart or ungroup it, so that all elements you want to populate are ungrouped on the first level.

    But then you don't benefit from the components approach. If anything is changed in a component you need to manually update all (unlinked) appearances of that component in your design.

    Axel Hermes supported this idea  · 
  7. 236 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Axel Hermes supported this idea  · 
  8. 56 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Axel Hermes supported this idea  · 
  9. 69 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Axel Hermes supported this idea  · 
    Axel Hermes shared this idea  ·