Comments
-
Hi Ilito, You could do it by adding a condition to every transition in the third workflow to only let certain groups or project roles execute the transitions.
-
Yes, you should be able to do updates, create new issues, etc. But you cannot do the administration from the Mobile app.
-
Yep - give that a try and see if it does what you want.
-
Hi Janek - Welcome to the Atlassian Community! That's certainly weird. If you create a filter- maybe something simple like key in (ABC-123, ABC-456) where 123 is a manually created one and 456 is an auto created one - then in the results of the filter displayed the Linked Issues field. See if you see any differences there.…
-
You can't verify it, but you can put the code in and then try to publish it at least. You can past the whole query here first if you want a set of eyes to check syntax.
-
Hi Florin - Welcome to the Atlassian Community! What happens to the issue when it is marked Approved? Does it go to a new/different Status? If so, then your rule should simply check to see if the issue is in that Status.
-
Hi Lakshmi Try something like: project = ABC and status was "BACKLOG" on 2023-04-01 That should show you every issue on that project that was in the Backlog status on April 1, 2023. Change the dates and status as needed.
-
Understood - I am just not understanding what you are looking for though. Let's say your checklist has 6 items. Are you looking for something that says there are 15 issues with number 3 checked and 20 issues with number 4 checked, etc.? Or something different?
-
Hi Madhura - Welcome to the Atlassian Community! I would try clearing your cache and/or try your browser with Incognito mode to see if there is something in the browser that is conflicting. Maybe even try a different browser.
-
Hi @CedB - Welcome to the Atlassian Community! Can you provide a visual example of what you would like to see?
-
Thanks, Andy! I have voted for the feature request and will follow.
-
What type of project is it? JSM? JSW? Team-managed? Company-managed? Do you use ScriptRunner (and/or Behaviours)? First, check this previous post and the answer from Nic - I suspect it is something similar. https://community.atlassian.com/t5/Jira-questions/Unable-to-edit-issues-in-a-Project/qaq-p/592208
-
Hi Khalid - Welcome to the Atlassian Community! Can you make NO edits to the issue? Or just can't change the Labels field?
-
That really doesn't make sense at all. Wondering if it is a browser thing. Maybe try clearing cache or try with Incognito.
-
Strange. I would try putting it in the advanced query, execute the search from there, then copy and paste the entire query into the Automation section and try the verify then.
-
Hi Smita, Correct, you cannot make the Epic a parent of an issue type that is above it in the hierarchy. The Bragi Initiative should be used for the Parent Link field on the Epic. Also, yes, there have been some rollouts for changes to Epics, especially Epic Name (replaced by Summary) and Epic Status (replaced by regular…
-
What do you mean by separate? Do you mean different issues should show on different boards? If so, then you need to change the filter for each board to include the component and/or team.
-
Hi Tom, Are you tying it from scratch or are you pasting it in from somewhere? If pasting, try typing it directly and see if that helps.
-
Can you post the rule here that you have so far? Your question says Auto assign. But then you say above that you want to move the ticket. What exactly are you wanting to do? When you say move ticket to Support Level 2 - do you really mean assign it to someone who works with Support Level 2? Or something else?
-
Certainly it was the Atlassian Intelligence (especially related to JQL!). Then the Confluence Whiteboards. Really cool stuff!
-
Hi @ADM Amar Msaid Try this: 0 0/5 8-17 * * MON-FRI - Every 5 minutes 0 0/60 8-17 * * MON-FRI - Every hour
-
Hi Tato, Not sure if I am completely following you, but let me ask some questions or repeat what I think I am hearing. You have a shared workflow. It is use in two different schemes. In both schemes the workflow is associated with the Epic issue type. Good so far? Then you changed the shared workflow and published it.…
-
Hi @Radka Matulova - I am marking Marcin's response as Accepted. Please let us know if you need something else with this one.
-
Hi @chakravarthysai mateti First, is it a Company-managed project or Team-managed project? I am assuming Company-managed since you created multiple boards with it. Boards have no magical powers for creating issues - boards simply show cards on them that meet the criteria of the board filter associated with them. So you…
-
Sure - then just a trigger type of Field Value Changed and select the field for that. Then add an If/Else condition to handle if it is Level 1 or 2.
-
Hi Gabriel, You should create a new custom field of Paragraph (multi-line) text type. Then edit the Default Value for the field to put in your “template”. Then create an automation rule to cope the value of the new custom field into the Description field when the custom field is updated.
-
Hi Sampath, You can create an automation rule based on an Issue Created trigger. Then add Conditions based on Components and Product Categorization as desired. Then add a new action for Assign Issue.
-
Hi Phil, No, the List view is not available for Jira Software.
-
Hi Corin, No you can't change the filter for the built-in board for Business projects. You can create a second board and modify the filter as you like. Here is some instruction on how to do that if want to give it a try:…
-
Hi @berecom One of the beautiful things about Jira is the flexibility. So you can design the board for whatever columns you would like. Just set your workflow with the desired statuses (they can be exactly the same names as your first screenshot if you like), and then modify your board to use the statuses of your workflow.…