Simmo Atlassian Team

@Michiel, nice idea! I'll keep that on the back burner for future innovation weeks!

Hi @Thomas Balasch, This is quite an old thread! The AUT tickets have been dropped in favour of the https://jira.atlassian.com/projects/AUTO/summary project. I'm not sure that this got traction. Best is to see if you can find it on there and if not, raise a suggestion/bug :) 

@David Meredith I'm afraid we couldn't find a JAC for it. The closet was https://jira.atlassian.com/browse/AUTO-490

Hi @David Meredith, I feel your pain mate. Unfortunately, this is a limitation with the smart value system and not just the lookup table. It isn't possible to refer to outside variables when you're traversing a list. I've tried to do the same myself. Our smart values guru tried to fix it during the last ship it but ran…

@Jennifer Luo and the order in .entries doesn't match what you see in the UI?

Hi @Jennifer Luo, I'm afraid that the order isn't guaranteed at this point. What is the issue with it being out of order? @matt.parisi you can't use it inside a list traversal operation currently. I'm hoping that should get changed pretty soon!

@matt.parisi you should be able to use it with the iteration logic, you just need to use the .entries property which returns a list you can iterate over. It has two properties, key and value.

I'll keep it in mind @Bill Sheboy. We've got shipIt coming up, so that might be something. Although I have another project in mind too :)

@matt.parisi the roll out has been slower than I had anticipated. Mainly, I forgot to increase it. Its currently at 75%. If you don't have it now you should by the end of the week. Same for @Jordan Wilkinson @Ashli Foust, @Sami Ahmed Shaik, I'm afraid that it is Cloud only at the moment. I'm not sure if the DC team will…

An update to this article can now be found at https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 I'm going to close comments as they're starting to get a bit unwieldily. If you're after support for this component, best to ask a new question or raise a support…

Hi all, I've been on leave for a few months so apologies for not getting back to questions. Thanks @Bill Sheboy for running point. We have innovation week again next week so I plan to work on improvements to the action based on some of these observations. @Bill Sheboy I'm not quite following the issue that you're talking…

Hey John, Afraid I don't have anything useful here. It really needs the component like Cloud has.

Hey @Darryl Lee, Afraid that Sam and I have no idea :) The server team is a bit of a black box to us since we split. Can you just raise the said suggestion?

I'd love to see a screenshot of the rule arrangement, that would help. Certainly using status.id isn't going to work. I think you may be right in that the scoping problem is dropping visibility of the table. I'll ask the smart values master about it. Update: confirmed that you're right, it is the scoping issue.

@Doug Levitt , an interesting suggestion. I want to fix the input has to be a string and not a number issue when I can, so i'll see what i can do with your request as well. This is my personal project so I don't get a lot of time to work on it. @Ingo Wenke , issue.status is actually passing in the status object (eg { id:…

I'm afraid I don't know @Yatish Madhav This isn't in my area of expertise.

Hey @Doug Levitt What is your use case for more than 20 entries? We did deliberately limited it due to the fact that it is allowing storage of objects, as the complexity and amount of data could spiral quickly. @Julia Foden, you mentioned 200, it sounds like you wouldn't be storing much in there? 

Another option, If you're OpsGenie, is to setup a roster and make an API call to the who is on call endpoint to get their account ID. I'm doing that at the moment for one of my teams weekly rosters :)

Hi @Julia Foden, What is the use case you have in mind that exceeds 20?

Hey @Dave Mathijs, At the moment, yes. It is on a per rule basis.

So there isn't anything for what you're after at the moment. You'll need to have the id of the Pr and fetch that information from Git using the send web request action I'm afraid.

Have you logged out what you're storing the email address as to be certain it is correct? Setting an email address for the user field should work on the Edit action.

How have you tried setting the email as the field value?

Hi @Nareg Karamanoukian, At the moment you'd need to do this yourself by sending a web hook to the repository API to fetch the info you're after. Which Git provider are you using? What are you storing about the pull request in order to be able to identify it?

Hi @Noelí Fusco, You can get a link to an issue with {{issue.url}}. If you're after an issue you just created then the smart value is {{createdIssue.url}} Thanks. Translating back via google..... Puede obtener un enlace a un problema con {{issue.url}}. Si busca un problema que acaba de crear, el valor inteligente es…

Right and thats not appearing in the Create issue field list?

Not sure I really understand the question here? There is a particular field that you want to populate?

I would suggest that you maybe raise a support case. Failing that, in the project where you're trying to create them, what are the sub task types? Have they changed at all?

Hi @Robert _Bobby_ Mittendorf, I don't think that this is possible at the moment. The approach described by @Mark Segall isn't going to work as our branching happens async, so your main line can finish before the branches have and variables created on a branch are only scoped to that branch. If it was just the last three…

Hi @Benjamin Leidner, Can you get their email address? It might be possible to use that to set the Supervisor? Cheers, Simeon.