Comments
-
Hi @Nikita and @Stefan Salzl - Since Nikita was able to create a workflow, it's likely she has global admin rights. But I think Stefan is on the right track - if you do not see a "Workflows" option under Project settings, then it's highly likely your project is team-managed, which can be seen at the bottom-left of your…
-
Hi - sorry for the late response. This is fascinating. I've never seen this interface in Jira, so I think it must definitely be a custom add-on that you have installed. If you go to your Manage Apps screen, there may be something about an FTP app there. Would love to hear who developed it, and what the original intent was…
-
Wait wait, am I the community leader? Heh. I guess that's me. Well, while leaders do have a Slack where we can chat with Atlassian Community staffers, and we sometimes get to talk to Product folks, we don't actually have a Batphone that hooks us up. Although what I really need I think is a Batdirectory. Bad metaphors…
-
Great topic, @Jimmy Seddon! Here's a pic of my current subs followed an overly long explanation (as I do): So, Spotify because as horribly tiny as their payments to artists are, I still feel like I'm hopefully paying them something or giving them useful stats they can track? Listening to music on YouTube like all the kids…
-
HA! Indeed, I wouldn't be able to be a community leader without my free (sometimes on trial for me to try the cool new paid features) Atlassian Cloud accounts.
-
Wow! Great find @Ryan Schamp !! Of course now I want to know: * can we help beta test it? * is there a way to build the lookup table programmatically, or via a web request? * when is this coming to production? But yeah there a LOT of if-else-else-else rules out there that would be much simpler to implement with a lookup…
-
Awesome! Glad to hear you got it worked out. Yeah, looking at the JSON, that looked just fine.
-
Hi @Jarrod Reimann Re: your error, that's telling you that you can't have the Field dropdown selector showing _and_ try to update it with JSON. If you just remove the dropdown selector (by unchecking it from the list of fields to set), that will get rid of that error. But I have a few other questions: 1. Is this rule…
-
Heh, yeah, I realize it's a bit much. But hopefully you or somebody else can make use of it!
-
OH, and for your purposes, you would probably still manually trigger it, but run it against a JQL lookup, so then:
-
Heh, I couldn't help myself. Got it to work, with the following caveat: * It only works if the field change was within the most recent 100 changes to the issue Anywho, we start with a Web Request to the Jira API: https://YOURSITE.atlassian.net/rest/api/3/issue/{{issue.key}}?expand=changelog Then we create a variable that…
-
Ah, more branches, more problems. The question I'd have is whether your branches can potentially touch different Projects, and where you have different contexts set up for the "Software" field, based on Project. Otherwise, yeah, that's weird why some options would not be available in Automation. If you could take some…
-
Ohai @Kelly Arrey and @Mikael Sandberg ... *TECHNICALLY* you could use the REST API to get the changelog for every issue, like this: https://YOURSITE.atlassian.net/rest/api/3/issue/BUG-5?expand=changelog And then, maybe, you could filter every change for a specific field... And then, maybe, you could grab the _last_ of…
-
There's a few possible reasons for the "Could not find create meta data for project/typeid" error: * The scope of this project is not Global or does not include all the possible projects in your custom field's drop down. * Issue type "Support" may not be valid for the CORETECH - DIVA project. I'm betting on the scope…
-
Ah, yeah, that will work because substringAfter is matching the first occurrence of your string. Nice one!
-
{edited to fix typo} Ohai @Andrew W Matthews -- Oof, I wouldn't want to be on the receiving end of a report about "Hey, the due date on this changed X times. What is the deal here?" That being said, sure - you could create a numeric custom field called "Due Date Tattletale". You'd need to set the Default Value to 0, and…
-
Hey @Srikanth Vemuluri - yup, there's actually a tutorial that addresses this exact issue here: * Automation for Jira - Send web request using Jira REST API For reference, the full API is here: * Update custom field options (context) For one of the calls, it was a bit tricky finding the "Context ID", which I recently wrote…
-
Hi @Chris Smith As @David Pezet pointed out, this can be done with replaceAll and the judicious use of regular expressions. So this worked for me: {{TOT.replaceAll(REM.concat("(.+)"),"$1")}} What it's doing is replacing REM and everything that comes after it, which is represented as (.+). We are replacing that with the…
-
Hi, the answer below from @Ste Wright describes how to do this in good detail: * Automation: Ensure All Children inherit the Epics Fix version You would simply need to use a Branch rule For sub-tasks instead of For stories and select the field you would want to update.
-
Or now that I look at it again, I think I misinterpreted "all match" as a lookup when it's just multiple conditions. Doh. But yeah, are you doing this in a branch?
-
Oh! Looking at your screenshot: The problem might be that you're doing this inside of a Lookup branch, in which case, you really need to be looking at: {{lookupIssues.issue.Teams}} Which (I THINK) will give you all of the Teams for all of the matching issues? Or you could probably more clearly list each issue with their…
-
So, I did some actual testing (imagine that!) and created a new Discovery project. Without me customizing anything, I now see this: But in Custom fields, I only see this: Which leads me to believe that "Teams" was auto-created. Anyways, the technique @Bill Sheboy referenced by looking at the API endpoint for a ticket did…
-
As always, "Yes And" to @Bill Sheboy. I would actually recommend that you consider renaming your Teams Checkbox field to something like: "Teams Selection" or "Team(s)" just to distinguish from it from the Team field used elsewhere: * The Team field is a custom field in Jira Software. (Advanced Roadmaps) OH but also I was…
-
Ooof. Yes, totally different order across multiple runs. What fun! :-P But ugh, that sucks.
-
Oh hey, I noticed that my two subtasks were created in reverse order. Did you create more than 2? And when you say "in any order" you mean it wasn't always highest to lowest? I'm guessing it's the unfortunate problem of Automation executing for each smart value asynchronously, or concurrently (both)? Man, how long will we…
-
Ah thanks for context. So if you are only defaulting to say, 10 core features at creation, will you be also be defaulting the other 40 options in the Descoped field? Just thinking about keeping the two fields "in sync". And is the plan to keep Scope as read-only? Because if not, as mentioned before, I think you'll need to…
-
Ohey @Derek Farr - Labels can't have spaces. https://jira.atlassian.com/browse/CONFCLOUD-37363 I guess they need to update the error messages for Confluence:…
-
And I would be remiss if I didn't point to a previous answer of mine that went through three other options for creating "dependent" fields: * Is there a way to make a user fill out a field based on a value selected in another field? The quick summary: * Jira Expressions - using third-party add-ons you can make a field…
-
Hi @marianna_taborda - welcome to the Atlassian Community! So neither Jira's issue create screens nor JSM's requests have the ability to create dependent or conditional fields like what you're talking about. BUT! Atlassian recently acquired ProForma which does have the ability to have sections with required fields appear…
-
Hey @Darrin Lillian - I hope this helps. I am very curious whether you'll be able to use it, and if you can clarify that every issue starts with all 50 Scope options checked. Also, it it pertains to my little rant the other night, I'd love to see what that looks like on the screen. Also, wonder if you will use the latter…