Comments

6 comments

  • Andreas Haugstrup Pedersen

    You can only get an item using the app_item_id. You'll still need the regular item_id for all other operations.

    /Andreas

    0
    Comment actions Permalink
  • Ronni Egeriis Persson

    Thanks Andreas.

    So I guess the workaround is to get the item_id by GETting /app/{app_id}/item/{app_item_id} and then PUT to /item/{item_id}. I think this is a fine solution, albeit it counts twice towards the rate limit.

    Thanks again.

    —R

    0
    Comment actions Permalink
  • Andreas Haugstrup Pedersen

    Yep, that's the way to go if you start out by only having the app_item_id (not a very common case). Get by app item id uses the large rate limit pool so you should have plenty of requests to work with. :)

    /Andreas

    0
    Comment actions Permalink
  • Ronni Egeriis Persson

    Since I want to grab the ID from the URL, the only way is to fetch by app_item_id.

    Is there a way, just as easy, to get the item_id? I believe the URL used to contain the item_id, but no more.

    —R

    0
    Comment actions Permalink
  • Andreas Haugstrup Pedersen

    If you're doing manual work, click the cloud icon on the right hand side of the grey action bar on the item view. That will give you the item_id to work with.

    If you're doing a browser plugin look for the item_id in the page DOM instead of the URL

    Unfortunately, most people are not developers so we cater to them. The shorter app item ids are better for most people in the URL. It's just us developers who would like the globally unique identifier. :)

    /Andreas

    0
    Comment actions Permalink
  • Ronni Egeriis Persson

    I see. I couldn't see that icon through the side-panel :)

    I like that my bugs app now have unique ID's per item. You cater to me too, there :)

    Thank you for your help.

    —R

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk