Jack Brickey Expert

So I actually found a similar earlier post I had responded to where I had referenced this open issue - https://jira.atlassian.com/browse/JSWCLOUD-21733 . I believe this relates to your issue as well.

Ah...hang on...I see you are on TMP. I need to assess the behavior on TMP as I rarely use them.

Hi @Daniel G , have you marked the "Epic Status" as Done (or similar closed status)? I also thought it would be good to share recent announcements about changes to the Epic behavior in Company Managed Projects - Upcoming-changes-to-epic-fields-in-company-managed-projects . Though tangential it is good info to be aware of.

Hi Ricardo, Primeiro, acho importante mencionar que a razão pela qual você geralmente não deseja que um problema JSM seja transferido do projeto original é que ele quebra a conexão com o cliente. Se o cliente fosse ao portal para verificar o problema que eles relataram que ele desaparecerá. Agora, deixe -me perguntar…

Hi @ricardo_santos , Se você está perguntando se pode fazer com que certas solicitações recebidas sejam direcionadas para um projeto diferente, em última análise, isso seria uma má ideia. Se ambos os projetos forem JSM, considere incorporar a solicitação digitada em um único projeto ou garanta que seus clientes tenham…

You can import issues from CSV and update existing issues. create-issues-using-the-csv-importer . While that doc is about creating it works for update if you include the current issue key in the import file. you could consider using the Jira API to update issues as well.

How many issues result from the filter? If you go to board settings and edit the filter it will take you to a JQL query. In that screen how many issues are returned? I suspect that you have crossed a threshold of the number of issues. You might also try another browser or clear your cache and restart your browser.

If you are saying that you have a label "shared" and you want to find all issues that have that label then the following JQL would work. labels = shared However, I suspect you're looking for something different. Assuming so please provide a little bit more details around what you are trying to achieve.

@craig.letourneau , please provide your current query.

OOTB none that I am aware of.

I do not have an open instance to the public. If I get time later today I'll give this a try. I will see if other folks can chime in here too.

I experienced the same as you mentioned. I assume you have verified each of the "back to the top" links are accurate? I am unsure why it is as slow as it is.

In case you have not review the docs on permissions or for the benefit of others - how-do-jira-permissions-work

In the bottom left you will see Company managed or Team managed project.

Hi @Yasmin Aylin , have you considered using the free Excel extension which allows you to construct and save a JQL within Excel? This allows you to quickly get the latest data from Jira.

Hi @Rale3R , it seems to work for me but maybe I missing some subtle detail here. On a test page I added an anchor and I referenced that anchor later in the page. I publish that page scroll down to the anchor reference and I'm able to click on it in a number of times and it'll take me back to the anchor.

Hi @maria lopez , if you are working with CMP projects then there will be an Epic name present. If you are not seeing this behavior please share full screenshots of example. In TMP the Epic name does not apply, rather the Parent field is used to connect a Story to an Epic. 

There is no way to restrict a comment required during transition for some users only. At least not OOTB. You could consider a different status that only certain users could transition to which would not require a comment.

Not ideal but maybe consider a custom date field and automation. When issue is linked and conditions are met then set date. This will allow you to construct a JQL.

I simply mean that as a site admin you need to limit who is given project admin permissions. Some projects can be handed off to capable users while others cannot. It really comes down to how your organization is structured. Some organizations have one or more site admins managing all projects (except TMP projects). Some…

There are two options. * Configure the issue types prior to import - remove task and only have "test case". * Perform a bulk edit after the import.

There is no way to configure limits (number) on admins. This must be managed by you site/Org admins.

Oh I see you are inquiring about an email response that has the old issue key. I need to test that. I suspect it would create a new issue in the old project but need to verify TBH.

Hi @pmarx , if you move a JSM issue to another JSM project then the issue key will change for the customer in the portal. So before the move their issue will show as oldproject-100 and after the move it will show as newproject-201.

Assuming this does not correct itself soon and if all users are experiencing the same issue, I think you will need Atlassian support. Can you open a support ticket under billing option?

I suspect you have gone beyond the Free user limits.

You my need to contact Support and enter a Billing question.

Hi @Yazan Qaraqesh , I am not seeing anything reported on Atlassian Status page. Would you mind sharing a screenshot of what you are seeing? Is it possible that you have more than 10 users and no payment submitted?

The behavior remains the same.

BTW, here is an import reference if you need it - create-issues-with-the-csv-importer . Export is simply done via the Advanced issue search page.