Jack Brickey Expert

You can't disable the Share with link unless something has changed I'm unaware of. Here in a good post on this topic that does explore a workaround and references an open request to boot - Is-there-a-way-to-disable-quot-Share-quot-on-a-JSD-cloud-portal 

Yes sprint names are auto-generated. anytime you (or other user w/ manage sprint permissions) creates a sprint in their scrum backlog then the system will create a new sequentially numbered sprint. Here is some documentation on Sprints but unsure if there are any details therein on the naming or not.

ah ok got it! So I would probably simply create a unique Issuetype for this called Risk. This would allow you to have a unique workflow and you can create the necessary custom fields to meet your needs. Example... * Title - this should be summary * Risk detail - this could be the description (my recommendation) or you…

you would need an app for that, e.g. Automation for Jira - trigger on comments added, condition if link exists, action copy comment to linked issue. Not sure that I should be but I worry a bit about performance implications of an automation that triggers on every comment. certainly would make it project specific vs.…

Ok Marine, I just tried this out on my NG project and got it to work. Here is what I did...

Hi Allen, I’m not sure what you are referring to here - “issue and risk”. Can you educate me? Is there some reference to this within Atlassian docs?

So I don’t use NG projects but have a test one I can play with. However I was not aware that you can create an issue in any column. Can you share a screen shot as requested earlier?

Link isn’t valid. Not sure what you are referring to here. 

Ok well if it is NG then the column heading is the status. So when an issue is created is it in fact landing in Design column? Can you share an image of you board where a new issue has been created AND the rule did not success for said issue? When issues are first created do they land on Design, I.e. is it the leftmost…

Seems odd on the surface. So I am assuming that Design is in fact a status and not just a column heading. Or is this maybe a NG project where the status = the column heading? 

You might find this post useful - JQL-for-issues-added-to-Sprint-after-sprint-start-date basically there isn’t an OOTB JQL and JQLs don’t return ‘sum’ results. Your best bet is sprint report AFAIK. 

Hi D X, so you are saying that all request types are associated with the very same Issuetype? And if you go to the customer portal and click on the lozenge in the upper right and select approvals some show and some do not and those that do not are of a specific request type?

Look into the Excel extension- /jira-cloud-for-excel-official 

The Commmunity forum is a user forum. I don’t know why you would be referred here from the support portal unless you are on Cloud- Free version but the tags indicate Server. 

I don’t see anything about status in your image. However, if you wish to have Status displayed on each issue in backlog then simply go to board settings and card layout and add the field. 

Here is an image showing where you should see the option to export to Excel or Sheets. 

I’m not sure where you are waning the status to appear. With that said the only value of displaying the status in the Backlog IMO is of you have more than one status mapped to the backlog. If it is a single status then I don’t see the point. Now, similarly for the active sprint it would really only make sense to display…

See if this helps - How-do-I-automatically-trigger-a-status-change-on-a-parent-issue 

Two options to try. * disable notifications for the create event altogether and add a post function to set assignee to reporter. * Add post function as in 1 but place after the generic event. TBH I have never tried this

Hi Paul, welcome to the Community. Sorry you are experiencing issues w/ posting. Indeed the Community anti-spam SW will often reject seemingly harmless text. Often it has to do with pasting something in which sounds like may be the case here. With that aside, it seems to me that for your issue you might wish to work…

True but you don't, I think, want an issue to transition to waiting for support anytime a customer comments. Generally the workflow is like this... * issue is in Waiting for support and agent needs more info from customer * agent responds to customer and causes a transition to Waiting for customer * customer comments back…

JSU, JWME and TBH I thought Scriptrunner would do this as well. Cloud has JSU built in and I use that all of the time. Regarding JSU.... When you edit the workflow and click on the transition of interest you should see Validator along w/ Conditions, Post functions, etc. Open up Validator and add validator. You should see…

is the status in "Waiting for customer" at the time the customer makes the comment? Please check your automations because this is where the transition on comment will occur. Check both New and Legacy areas.

yep. that is precisely to the point i made... Things to keep in mind if you migrate from next-gen to classic <<<<<<<< SNIP >>>>>>>> * Epics: Jira moves your epics across if you map them to an epic issue type in your new project. But, you'll lose the relationship between your epics and their child issues. The child issues…

Hi @Renato Osorio , you indicate you have tried everything but what exactly have you tried? Can you share a screenshot of your layout screen? Click on the Configure link while in issue detail view.

Hi @Magdalena Migas , I'm not sure I understand your goal. Your JQL looks correct from what I was thinking your goal was so obviously I don't understand. You mention getting issues returned that are currently in states other than "To Do" so maybe you want to only show issues in "To Do"? project = "XYZ" AND status = "TO DO"…

well you can have a group defined for this and you can have a permission scheme that you use to assign to each project but ultimately this is by project.

well dang it... I was scratching my head until I took a moment and looked at the tags on this post and I now realize you are on Server. I should have seen that from the start. :-( So I really can't assist on this but I will ping other Community Leaders to see if they might be able to. Also, I would recommend reaching out…

i haven't done this but since Epics in NG don't have Epic Link (or has this changed :-)), I would assume the following to be the right (?) approach.... * Move the NG Epic and ensure it is clean and has the desired Epic Name. Actually, I might even consider creating a new Epic in Classic. * Move over your issues and use…

Here is an old post I would refer you to - Merge-2-Atlassian-Cloud-Instances. It refers you to this article - merge-multiple-instances-of-jira-cloud If one of the instances is rather small (few projects/issues), it might be best to simply create the new projects in the other instance and then use CSV export/import.