Jack Brickey Expert

I don't understand your question. Let me try to give a theoretical (but stupid) example... rule 1 * trigger - issue created * condition - type = improvement * action - transition issue to "in progress" * action - edit issue "loop count limit" incremented +1 rule 2 * trigger - issue transitioned * condition - field…

There are a number of posts in the Community suggesting the solution of using opsbar.sequence properties for this. Now at one point, this was broken but it may be resolved now but I have not attempted since I found it broken. I have included some posts on this below. Give it a try and please post here your results.…

So what I would do is to remove the field entirely from your Suggestion screens. I assume the Scope is required at Create or is it at some other transition? Assuming it is at Create for your other types then consider creating a Validator in the Workflows for those types on the Create transition. In this solution you do not…

I don't know of any specific example. Below is the rule setting that allow a rule to be triggered by another rule. If you could detail your goal maybe I could assist further.

Hi @Karine Igityan , welcome to the community. I am not following your question here. Could you please restate and explain in more detail?

You are not blind. The app does not currently support that it seems. You may wish to provide feedback to Atlassian.

Hi @[deleted] , welcome to the community! thanks for all the details on your post. However, I wonder if you could simply state your question. Are you asking how to make the Scope field required on one Issuetype? Or something else?

You can create multiple rules where one would trigger the other.

You can remove the Labels field from your screens. Some system fields cannot be removed, e.g. Summary obviously. The bottom line here is if it is listed on your screen then you can remove. Warning: if this is a shared screen scheme then changes will impact other projects that use the scheme. To avoid use a dedicated screen…

In Free you cannot. Have a look here - Changing-your-Cloud-site-name-url 

In TMP you can use "parent" in your JQL for finding issues associated to an epic... project = myTMP and parent = ABC-123 Where ABC-123 is your epic. 

I am unaware of any such support. What exactly is your goal?

Duplicate post

That is indeed a TMP functionality not available in CMP.

Hi @Desiree Meijne-Schmit , it is simply allowing for parallel sprints. You can find out about running parallel sprints here - https://support.atlassian.com/jira-software-cloud/docs/use-parallel-sprints/ 

This would need to be done via the API. I have had to do this when importing via CSV. 

The only option to hide certain issue from users in a project is by using Issue Level Security scheme which works based on issue type. Do you really need to hide issues based on assignment or would it suffice to restrict transitions based on assignment?

The closest solution, but not precise, is to make them a Trusted user. 

You can’t achieve that without an addon. 

potentially a browser interoperability issue. Are other browsers experiencing this issue? Which browser is this? Clear cache?

It will continue to work as is. Obviously if you run into a bug, limitation or odd behavior you are stuck with it. Though you could always self-support as the code is available.

Is it possible that you have some recent addon app? I have never seen anything like what you were presenting in the image here. While it could be some recent roll out of Cloud functionality I am more suspicious of an add-on.

I just found the open suggestion for adding components to TMP - JSWCLOUD-17601 . You may want to vote and watch the issue. However that's not gonna help you in the near term. So yes CMP is the only solution if components is required.

@Carlos , what exactly changed to result in receipt of emails? Was it whitelisting Atlassian or something else?

It could be that you were on a TMP project. Can you verify by looking on the lower left corner to see if you see team managed project? When I last checked components was not supported in TMP.

This field is only required if you intend to use a folder other than the "inbox ". If you intend to place your incoming mail into a folder then you need to specify the folder name here.

Hi @Sindhuja Guttina , welcome to the community. So I'm not 100% sure exactly your goal. However if you are saying that you want to have your closed status not associated to your board then, assuming this is a CMP project, you can simply not map the closed status to any column. if the above does not address your question…

When you create a new CMP project you can choose to use an existing project as a 'template'. However, it does not create an exact mirror of the other project and that includes the board. So the bottom line is that you will need to recreate your board which can take a bit of work if you have a complex board but certainly…

It may be that your projects are TMP or if CMP the may not be Software projects. What you need to do is to create a filter that captures all of your desired projects (projects in (a, b, c,...)), save it and create the board from your filter.

Hi Morgan, Unfortunately there isn’t a way to configure that.