Jack Brickey Expert

Hi Tim, welcome to the Community. You really should not move an issue between projects as it breaks the connection with the customer who reported the issue. Rather, I recommend you create a linked issue to the other project,

It may be that there is an exclude property on the transition to Closed. Check the workflow. Here is an article that might help - workflow-properties 

Great! Sorry for the delay in getting back to you.

There are two ways to accomplish this. * set up automation to run daily and check for issues that are on hold for >24hr * set up an SLA that breaches after 24hr in On Hold then use automation to email customer when Breach occurs I prefer the later option as it is cleaner and hit precisely on the desired timing. 

Jira doesn’t have a formal concept of sub-project. I would consider Epics to be project within a project. 

just for grins to help w/ isolating what works and doesn't can you remove the 'noise' and just do this... comment ~"A31122019 -B31122020"

Here are my thoughts on this. But before sharing, please be sure to search the Community for similar posts/discussions as there have been a number on this topic w/ good answers/opinions/discussions. * Generally speaking fewer projects is better than many but there are most certainly exceptions. * If you have independent…

Not yet. If/when it shows up it will not be as feature rich as Advanced Roadmaps in Premium. What that means exactly is as yet unknown (by me anyway).

@Monique vdB, how is the Unanswered sidebar fed exactly? Most recent, oldest, cherry picked by Atlassians, etc?

Awesome, have been excited about the arrival of this feature. I think it will add a lot of credibility to the Community.

I assume you have been able to add user to this project previously? There was a reported issue on this a week or so back but I thought it was resolved. If you are able to reproduce please let me know.

I have never experienced this TBH. You mention changing employers, does this mean you are seeing on different instances of Jira? If so, have you tried different browsers? If you are seeing on multiple browsers please report to Atlassian Support.

Hi Brian, welcome to the Community. That sure seems odd as stated. Is this reproducible? If so please share more info. It may be that you will have to work with Atlassian Support if reproducible as they can log in and observe.

Hi Daniyar, welcome to the Community. In what view do you wish to hide these issues? If you mean you wish to make them such that a user cannot search and find the issue then that is not possible; at least OOTB.if you wish to simply hide them in a give filter result or board that would be possible. You could consider moving…

Can you share your exact JQL to see if I have any thoughts?

Hi Tomasz, are you asking why Customer users can’t see issues reported by other Customers? If so maybe this will help: * use Organization feature to group your Customers under organizations * issues reported by a Customer need to be shared with other customers so that they are Request Participants see if this article helps…

You can edit your workflow and add a Condition to each transition that you want to restrict. You will need to create a group and add members to that group that will be allowed to transition. You will use this group in the Conditions you set up. 

you can run parallel sprints which will use the single backlog.

Automation using cron is UTC based.

Hi Uday, under Related Content in the right-hand sidebar I found this post How-to-Prevent-Close-of-Epic-Until-All-of-its-Issues-are-Closed Which offers a Scriptrunner code example. You might give that a try.

Hi Malik, welcome to the Community. If this is something you need only occasionally I would recommend using excel. Export your list of issues or use the Jira extension for Excel. This will allow you to create the desired charts. If you need this regularly then consider creating a custom drop down field that has two…

It is very likely that one instance is a newer instance. I have noted some differences with the newer instances. Sometimes these differences catch up as the older instances are updated but not always.

go to project > Project settings > Permissions. Edit the permissions and add the group to the specific action, e.g. Browse, Comment, Create issues, etc.

you need to ensure the user is not in any Role or Group that might be leveraged in any project. Put this person in their own group, e.g. create a group for that client/project - Projxxx-client-group. Then give that group the desired permissions/notifications.

here is how you do it for a Classic project... for NG just edit the summary of the epic.

Hi Moe, so i expect what you have implemented on one or more Classic projects is that you have created a custom field that has some drop down selection representing teams. Then you have some boards created that represent the various values in this field so that each team has their own board? Assuming so, you can create a…

Open the Epic and change the Epic Name field.

This is not possible in NG projects.

Hi Jane, in Cloud if you are trying to change the Project Lead you should find this under project > Project Settings > Details. Is that your goal?

You don’t assign “teams” to an issue. Issues are to be assigned to individuals. what exactly is your goal?