John Funk Community Champion

Hallo Andreas - Willkommen in der Atlassian-Community! Sie sollten in der Lage sein, den Link einfach zu entfernen.

Hi Scott - Why would you want to see closed tickets in the Backlog? They are probably in a Done category status such as Done or Closed, which would be mapped to a column on your board and not the backlog. 

This seems like a bug if they are requiring you to put in a Summary for an update. I would submit a support request to Atlassian. Please update here with the resolution for future readers. https://support.atlassian.com/contact/#/

Did it do any update to the issues? Did it create new issues?

Hi Garrett - thanks for the opportunity! I will give it a whirl. :-)

Okay, that should be fine. You should be able to create a Scrum board that uses a filter that includes multiple projects. 

Did you click on the boxes for each one for Map field value? 

The only workaround I know of is to create a Company-managed project instead. :-(

Are you trying to create new issues? Or update them? If update only, is the key one of the columns in your CSV? 

Yes, I saw now where this is a new feature they are rolling out. You should be able to remove the field from the Create screen if you do not desire it there. 

Correct.

Hi Jurgen, Can you share the automation rule that you have built so far? Also, what is not working with it?

Hi @Maktumhusain Taseeladar Since they are different dates, the best way is to do a CSV import with just the issue key and the two dates. 

Hi Jean-Michel, Agreed - but unfortunately that is not currently available - it operates as an OR function only. 

Best team in the world - literally!!!

Hi Erin - Welcome to the Atlassian Community! Can you share your Rule? Also, I wrote an article earlier this year on creating recurring tasks with automation: https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

Knock, knock. Who’s there Saul. Saul who? Saul there is. There ain’t no more.

Hi Saira, Can you not remove the field from the Create screen for that project? 

Hi Anuradha, Can you be more specific? 

I would suggest opening a support ticket with Atlassian then. https://support.atlassian.com/contact/#/ Please post back here with the resolution so future readers can see. Good Luck!

Hi @Nathali Pflucker - Did Clark's response answer your question? 

Just saw the clarification below. So just change the Issue Type in being created to Story and get rid of this advanced code, and you should be good. 

So all of these sibling sub-tasks have the same parent I assume. Is it possible that it is returning more than one project? Is this rule for a single project? 

That one has be baffled as well. I don't know of a reason it would reorder those. :-(

Thanks for the further explanation. Maybe implementing some re-fetches between steps would help as well. 

you probably just need to open a support ticket with Atlassian. https://support.atlassian.com/contact/#/ Please post back here with the resolution so future readers and see. 

Well, if you order by it, then that achieves the grouping more or less because all of the issues will be in order by assignee. I am curious as to how that does not meet your need. 

I was able to use a multi-select user field in the custom field:

Hi Clay, Next-gen projects have been renamed to Team-managed projects. However, you won't really be able to do "swimlanes" as such with those. I would suggest you create a Jira Software Company-managed project. So, click on Create project like you did, then select Jira Software. Then click Kanban (or Scrum if you are using…

You might try going to the Permission Scheme and then using the Permission Helper. It will ask for specifics such as the permission (maybe use Edit Issue), the issue key, and the username.