David Niro Atlassian Partner

Hello @Andrew Beaudry , welcome to the community! The link in this step was whatever custom issue link Jeffrey was using. Could have been "blocks", "implements", etc. When creating the Extend Generator, he would have had to select the one he was using and the direction. @Sachin Mistry , Automation is part of Structure by…

Hello @Iris Barr , Welcome to the Community! This would require the issuelinks attribute to be available for use in Structure Cloud. Unfortunately, it's not available yet. We do have a task related to this and I have added your vote. I will follow up with you when there is an update to share. Best, David

Hello @Marta Elicegui , Unfortunately that is not yet possible on Cloud. However, it is one of the top items on our roadmap and I have added your vote as well. As soon as there is an update to share, I will follow up here. Best, David

Hello @Sven , Welcome to the Community! I believe what you will want to do is use the #children modifier. SUM#children{storypoints} Please let me know if it helps! Best, David

Hello @Marta Elicegui , On Cloud, the Time in Status column has an option for "Current Status". You just need to toggle it on when adding the column. Best, David

Hello @Alex Agn , Yes, it works with the updated field. You would want to switch the updated and today() variables though. Best, David

Hello @Santhosh R Bhat , I am happy to report that it is now possible to add Gantt Attribute Columns to Structure!! Please let me know if you have any questions! Best, David

clarification project.lead will work if you are looking for the project lead at the issue level. this.lead will work if you are looking for the lead at the (group by) project level 

Hi @rupert.schreder , This is going to depend if your Jira instance is hosted onprem or cloud. IF it you are onprem hosted, you can use a formula column with the following as the formula: project.lead It makes use of the Property Reference for the Project item. On cloud, this property is not available (yet). To check if…

You're very welcome! Please let me know how it goes!!

Hello @Daniel , There's no timeline to share on this. Could you share some information about the generators you have set up? Generally what we see is that introducing the duplicate issues can be avoided, negating a need for the Filter that Parrish references in the original post. For example, if you have an Insert…

Hi @Diana Gorv , Sorry about that! Yes, but it is ELSE IF ELSE IF statuscategory = "DONE": LAST(sprint.name)

Hello @Diana Gorv , Something like this may work for you: with _assigned = sprint.FILTER($.state = "active" OR $.state = "future"): IF statuscategory != "DONE" AND _assigned.SIZE() > 0: _assigned.LAST() ELSE: "Backlog" It uses FILTER() to reduce the array of sprints to only those that are in an active or future state. But…

Hello @Parveen Taj , In your formula, instead of Sprint = Sprint.FILTER($.state = "active"), try: Sprint.FILTER($.state= "Active")!= undefined Best, David

Hello @Visa Kask , Welcome to the Community! It is possible to do this using Formula Columns. We just need to count the number of issues and divide the sum by the number returned. A quick example is this: with _children = COUNT#children{1}: IF _children > 0: SUM#children{storypoints}/_children If an issue has "children" in…

Hello @Krishantha , If you mean Structure by Tempo - Jira Portfolio @ Project Management PPM, you can reach out to our support team through our customer portal, support.almworks.com. Best, David

Hi @Parveen Taj , No, there is not a way to apply the color to the entire row. For visibility, you could move the column in front of the summary so it's one of the first things to catch someone's eye.

@Parveen Taj , glad it's working for you now! for context on why the original formula wasn't working for you, there are some differences between Cloud and Onprem formulas. The original formula I provided was written with Cloud in mind, but if you see "Automation", you are actually on an Onprem hosted instance. Best, David

Hi @Parveen Taj , That's interesting. In your structure, do you see a button at the top that says "show generators" or do you see an option for "automation"? Glad that you were able to get to a working formula. Sounds like you will want to use FILTER() rather than LAST(). It should look something like this:…

Hi @Parveen Taj , For this, you will want to take advantage of the Item Properties for Sprint and the FILTER() or LAST() function to identify the Sprint you want to highlight. Then, Markdown can be used to add the color to the returned value. A quick example that you can use as a reference would be something like this: IF…

Hello @Amelie ! Welcome to the Community!! When Adding a Generator to a structure, on-prem, you will want to select the name of the structure from the top row before selecting "Add". In your case, it would be the "DSRHC Struc_Test" text just above the "Insert Issues:..." generator. Hope this helps! Best, David

Hello @Surekha Gupta , If "Code complete Target date" is a date field and you have Treat Parent Issues as Groups option enabled, this should work. Hope this helps! Best, David

Hi @Brian Lehmbeck , Posting here as well in case others are looking for similar information. Thank you for working through this with me! As you identified, the reason the formula was throwing the error was due to there being more that one fixversion on some of the issues. We were able to resolve this by using a unique…

Hi @Milan Pekař That is very strange. Please reach out to our support team directly via support.almworks.com. We will want to have a closer look at what is happening. Best, David

Hi @Milan Pekař , Ok, you are definitely not on Cloud, so you should be able to pick History from the list of attributes. In your previous screen capture, where you see history, click on the "Manual Specification" option under it and start typing "history". The correct option should present itself under the Standard…

Hello @Milan Pekař , If it's not recognizing history, you may be on a Cloud hosted instance of Jira. If this is the case, history attributes are not yet accessible. At the top of your structure, do you see "Show Generators" (Cloud) or "Automation" (DC / Server)? If you do see "Automation", history should be working and it…

Hello @Johann Venambre Do you mean that the link that your formula returns redirects you to the Jira Issue Details page and you would prefer if it opened the Grid + Details Layout in Structure instead? If I have that right, unfortunately it will not be possible. If I have it wrong, could you clarify your goal? Best, David

Hi @Tomas Lynn , Welcome to the Community! The issuelinks item property is not yet available on Cloud, which is the hosting platform you have tagged. It should be giving you red text as an unknown variable. So, if you're not seeing that, maybe you are not on Cloud. Either way, we should check before we proceed. If you see…

@Brant Schroeder I think that may just be the way the two screenshots are lined up. It does appear we are looking at two separate structures based on the start of the JQL that appears in the first screenshot and the second. What we can't see is the Extend Issues Under Epics generator in the structure that does not show any…

Hello @Paul Doman , You're very welcome, and thank you for the additional context! Please try: PARENT#level=2{summary} Since the value you want is the summary of the Group, and from what I can see the level of the group is 2 in your hierarchy, it should work for you. More information on the PARENT{} function and #level…