John Funk Community Champion

Thank you @Nic Brough -Adaptavist- and Happy Birthday!! You were also the first person I remember answering my questions. You are certainly one of the giants of the Atlassian Community!!

It might be because you are cloning a ticket that is in a status that doesn’t exist in the target workflow. I have seen that already this week in another post. So there are a lot more fields getting cloned other than just the project. I suspect it is the status.

😁

Hi Gisele - Welcome to the Atlassian Community! Is the email address of the user getting captured as the reporter of the request? If so, you should be able to send emails to the Reporter. 

No worries. The Field Configuration tells the system what fields should be required when the issues are created. It also can be used to help text for the field. But the Field Configuration is actually created for one or more issue types. So if you want the Description field, for example, to be required for all issue types…

Hi Todd, You can use the bulk edit function manually but with only 1,000 or less at a time. Is there a reason you have to wait and do them all at once? Can you not do them gradually through the year? And you could still use Automation For Jira but you just need to base it on a query that only does about 1,000 at a time. 

Thank you, Reynalda - I am happy to help. :-) Did the document help you to understand better? Do you still need additional help?

Hi Julien, Every user must be in the jira-users group to be able to access Jira. It sounds like the issue is with each Next-gen project. You need to go to Project Settings > Access for each NG project and adjust the Project Access - it is probably Open right now. Change it to Limited and then designate who has access to…

Hi Marcilia - you don't need to create multiple questions with different languages. We can help with whichever. I have answered you in your duplicate question posting here:…

Hi Samuel, If you don't have a + symbol at the top by the other tabs, then you don't have permissions to create tabs for that Team/Channel. Find the administrator for that Team and have them add it. 

Hi and Welcome Alan! We are glad you are here!

Oi @Marcília Nascimento Em que você deseja que o filtro seja baseado? Criada? Acabado? Algo mais? De qualquer forma, seria algo como: projeto = ABC e criado >= startOfMonth () e criado <= endOfMonth ()

Glad I could help. :-)

I don't feel like I was much help, haha. But I didn't have any better news for you either. 

You could do a single rule but have nested if/then statements for each Request Type. Then Copy and paste the email under each Request Type and edit out the fields that would be blank. 

I don't know of a way to "count" those other than create some additional statuses and move them to different columns so that any one column doesn't have more than say 10 in it. 

There is an existing request here: https://jira.atlassian.com/browse/JRACLOUD-74384 You should vote for that and follow it there. 

I think you might be talking more about columns instead of swimlanes. But either way, the user should be able to see visually exactly where their card is in the list. Unless they know how fast cards are moved out of that lane on average, it does them no good to know how far down they are until they get close to the top. 

Does that issue type use a different workflow in the two projects? 

Hi Blake, You need to edit the property of each Transition and give it an opsbar-sequence number. To change the order of transition buttons: To change the order of transition buttons, including additional transitions in the Workflow menu, add the property key opsbar-sequence to each workflow transition that you wish to…

Great! Glad I could help a little. :-)

Hi Adria - Welcome to the Atlassian Community! I am not completely following your question. The Swimlanes already have a number for every card in that Swimlane. I am not sure why you would need to know that your card is number 11 of 27. 

Here's my advice. Create the worfklow as this: Created-->Assign-->Pending-->Resolved-->Closed 1. The card is created and goes to whatever status that goes to (i.e. the first status - Created). It is not assigned to anyone. 2. The user pulls the card they want to work on to the next column (this would be the next status in…

Hi Griffin - Welcome to the Atlassian Community! Who are the issues assigned to in the non-Epics cards? 

Sure - here is the link to the Field Configuration guidance. https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html

Ah just noticed that the above error you mentioned also mentioned issue type. So make sure that the issue type is available in the MI project - the issue type used in BPO-207. 

You are welcome! Is this all taken care of for you now?

Why not just have Closed as the last status and not use the Done status at all? Then you can set the Resolution field to Done or Rejected or Obsolete or whatever you want. Just make the Closed status a Done type status category. Just some thoughts - but definitely do what works best for you and provides you with the best…

Great! Glad I could help a little bit. :-)

There needs to be some type of linkage between the two issues so that the triggered issue knows exactly which other issue to copy from. But yes, you can do that. :-)