Comments
-
Sure! If you can hit that API in the same context as your scriptRunner code you can surely share the responses :)
-
^ This
-
The JavaScript charts could indeed help you out here. It should however accept standard JQL 🤔What query are you testing to drive the chart?
-
I finished my MsC in Robotics nearly a decade ago and had to drop the dream of getting into my PhD on composite materials due to lack of funding -> Work on! Since then my life has taken a turn or two :) I think I'd go back through the project management channels, focused on enterprise software.
-
I'm looking forward to meeting you face to face (summit maybe ;) ) and hearing your side of the story on the acquisition :)
-
Hello @Jeremy Burton, From the screenshot you share everything seems correct. You have the filters at the top correctly driving the plan view: * Test Release filter selected* All epics of that release visible * All projects* Epics gathered from all projects for that release
-
If you ever take your team to australia, go lawn bowling! :D
-
🤣You heard the man @Tim Keyes Rest it is
-
Welcome @Esme Crutchley !!!
-
Glad to hear this!! Thanks for updating the thread with the solution 🚀
-
In spain we call it 'mimic' (mimica)! And yes, it's an awesome game!!!! Now a days I actually play 'Times Up', which combines Taboo, charades and memory 😍
-
😄Awesome stuff!!! I still dream of someday going back to uni as a fulltime worker... maybe someday :)
-
Not yet :) https://www.atlassian.com/blog/announcements/welcome-code-barrel-automation-for-jira
-
Thanks for updating the thread with your findings! They'll surely come in handy to the next one following your steps :)
-
Hello again, I see two things here. First, a side note. You are adding an expand query parameter on the Transition POST function. This will not do anything in particular. It is only part of the Get Transitions API. Secondly, I can't see the body you are sending with your POST request. This is where I believe the crux of…
-
Good question 🤔 @Nic Brough -Adaptavist- , thoughts on this?
-
Might be a terrible idea but, have you tried to add a waiting timer after the creation to ensure the parent-subTask links are created later? (given the validation you made that at a later point in time they are there)
-
Hello @Michael Littlewood I would go with something like: project = MYPROJECT AND status WAS "QA Work" BEFORE "2021-01-01" That way you can find all the issues within a project that have been in a particular status before a particular date (stating the future will give you all the past). 🚀
-
Well, potentially (potentially 😋) you could do this with ScriptRunner. On issue creation/update you could look into the sprint value and the make the appropriate requests to grab the Sprint goal and add it to the custom field :) https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=cloud&tab=overview
-
Hello @Siri Nama My first option would be to create a new dashboard for this. You can create one similar to created/resolved based on a JQL filter that gives you the timeline for issues resolved over a period of time. It's not exactly what you are after though, it would be the reverse.
-
Hello @Ermelie Lising Can you give some more context on this question?
-
Hello @[deleted] Can you share with us the REST call structure you are using? Description fields should not disappear when transitioning, you are completely right there.
-
This can be achieved through some sort of automation tool. The ecosystem, Jira Automation (by CodeBarrel) could very well serve your purposes here :)
-
Hello @Daniel Reyzman Can you share what status these lost stories are in when you reach them via URL? If they are DONE, they might very well not be visible.
-
Hello @Josh Peterson What do you mean with 'In other versions of jira I've used, this is a more central feature.' ?
-
Hello @Matthew Buehs Your JQL is nearly fine. I believe you are missing a sign -+: `(startOfWeek("+6d") OR startOfWeek("+7d")) AND...` See docs: https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-functions-reference-764478342.html#Advancedsearching-functionsreference-startOfWeekstartOfWeek()
-
Hello @Michael_Tan I can think of two ways to do this. If your web-item displays content in a glance, you can set the trigger on render (when the glance is open). If it renders a button or something a like, you can trigger directly from you button code