Jack Brickey Expert

You probably have a post function that is overriding the chosen value. Edit the workflow and open the transition to done and check post functions. In the new issue view the resolution will always be there by default. 

Well for Classic it would be Epic Link is Empty. But for NG you can’t use that as the epic link is empty for all issues. Odd I know. They are working on a solution last time I checked. 

You can reach Atlassian Support at support.atlassian.com and click Contact. Unless you are on free version in which case you are relegated to this user forum. 

In Cloud if you click on the filter and get the results then you should be able to click on Details link at the top of the page and edit the name there. Unsure if server has same or not. 

I would recommend you reach out to Service Rocket and or Atlassian support on this issue. 

Deleting issues is a bad idea in and of itself. With that said I expect that doing so on such a large number has a high statistical chance of failing. If the failure continues to occur, I recommend deleting maybe 100-500 at a time.

By chance are you listed as a customer in the project as well? 

The image above is of the billing info. Where are you trying to add users?

Sure you can do that. Refined Theme solution in the marketplace is an example of such a solution so no reason you cannot do so as well. You can go to the Atlassian developer site to get started. 

This is not possible. The functionality is limited to the two fields unfortunately. There is a suggestion her you may wish to watch/vote. CONFCLOUD-31867 

Customer notifications are configured under project settings > customer notifications not under project settings > notifications which applies to licensed users of the application. You can’t setup a specific notification on a customer by customer basis. one thing you can look at is using the built in automation to send…

This is controlled under the global permissions under Jira settings - managing-global-permissions 

If you are not the Jira admin please reach out to them to investigate if they can access and assess the reason.

It sure seems like a permissions issue with the target project especially if you are able to move the issue to other projects. Might be interesting to create a test issue in the NG and try to move to a different project and the from there to the original destination project. I am able to move issues NG —> Classic fine. 

You can’t have it both ways. You can’t allow customers to include non-customers but prevent non-customers from joining. This is controlled under project settings > customer permissions.

Only with an addon, e.g. Tempo.

So the project is listed and if you click on it you get the error screen? I wonder if the project somehow has a permission scheme that equates to ‘archive’, I.e. no viewing permissions. Is this reproducible, i.e. have you tried creating another project? Can you create a NG successfully? I would reach out to Atlassian…

If you move the task the sub-tasks should move. At least that is my last recollection. 

Can you go to the Projects page and see if the project is listed? Did you create the project or someone else. Are you a system admin? Generally create projects is restricted by the admin. Often they allow individuals to create NG projects but not Classic.

Check that you have move issues permissions in the from project and create issues permissions in the to project.

link updated... If you are on cloud you can use “create linked issue”. Here is an article - create-a-linked-issue-to-collaborate-with-other-jira-product . By using this you can easily see the link in the issue allowing you to navigate between the two. as Far as the automation it depends on your exact goals..

I understand that there will be 5000 for JSD and 2000 for JSW on the Standard plan. At least that is how I read the email that came to me. I agree with others that the limits are way to restrictive however, I will not upgrade to premium regardless as the value simply isn't there for my situation. It doesn't mean I don't…

I’m a bit confused by what transpired to get you where you are. Regardless, you have a couple of options: * change the workflow associated with the current Issuetype to align with your needs. This could simply be by associating the old workflow with the current issue type. * move the current issues from the impediment…

looks like it. Note that this was announced by Atlassian as they are integrating into cloud by default. As an A4J Lite user I received an email on this a couple of weeks back. I would reach out to Atlassian Support and see if it is integrated and they can update your instance. It might not be ready for release just yet and…

feel free to vote/watch - JSDCLOUD-3325 

please provide a screenshot of what you are seeing.

feel free to vote/watch this and the linked issues - JRASERVER-68371 

it is per user and associated to a specific email.

Request participants are used for Customer (portal/email only access). If the person is a JSW licensed user you can ensure they are in a role/group that has browse and comment permissions. You can then add them as a "Watcher" which will allow them to access the issue from w/in the application. Regardless, if they are a…

no custom window curtains for free version. :-(