Jack Brickey Expert

Do you mean this

@Tiffany& Atlassian Confluence Team, I really appreciate the transparency and simplicity of your post. More importantly I am pleased to see that Atlassian is listening to their customers. I never doubted that you were but this post confirms it. While personally I love the new editor, I also appreciate the pains that many…

Can you look at the history on one of the ‘mysteriously’ assigned issues and see if there is a clue as to how it got assigned/unassigned if in fact it even did? A screenshot shot of that may help too. 

My guesses: * some addon conflict * some automation you have setup is causing this * a very odd bug can you ponder this and provide further thoughts? When did this begin? Does it happen for a specific user or all users?

Yes and that is how it is by default. If that is not happing for you then you must have some rule set up to assign. Check the manage rules under the ellipses in upper right of board.

Edit the issue in detail view click in the Assignee field click the x and you are done

You should have been presented the option at the time of creation but not to worry you can edite after the fact. Go to Jira settings > Issues > Custom fields and find you field. On the right you will see ellipses, click there and select Contexts and default values then click on the edit in the next screen.

It is odd that you do not see the JSW. That would seem to say that A4J does not have permissions to create issues in the JSW project. Please ensure that it does.

Keeping my comments in this thread... so I guess that server is different as I see this ... so let’s cast the OOTB aside for the moment and check A4J assuming it is still installed.

Hi Kim, if you are an admin please view email logs - project settings > email requests and click on view logs for the email being used.

are you using the magnifying glass or JQL search. Please try the JQL search.

Yep but also consider: watching, using tags, flags coupled with filters and Star the filter. The key thing about starring issues is the maintenance associated with removing them. This could become tedious.

@Julie d_Antin _Elements_ , but why would this work where the others would not? I think we need to understand Devops requirements and roadblocks before recommending another addon. The thing that strikes me here is that they have not been successful with 3 capable methods so I have to wonder if something else is goin on…

Thanks for sharing. TBH, I have never even played with that so learned something new. 🙂 regardless, I’m betting this is only accessible under the “starred” list and not at the detailed issue view. I did a quick search in the docs But not much info -get-home-search-or-create-with-the-global-sidebar 

We need more info to help... * did this failure to add issues just start happening ‘over night’? * are you an admin.? If not please check with your admin on any possible changes that might explain it * can anyone create issues? * have you tried other projects? depending on the answers you may need to contact Atlassian…

Hi Jose, we will not be able to access your instance to observe what you are seeing. Consider a screenshot instead. I am not aware of being able to star an issue. You can star (favorite) a filter, board, etc. Note too that the ⭐️ in the left sidebar is moving to under “Your Work” in the new navigation view that is in the…

What do you want to change it to? There is an article (below) about verifying your domain so you can use it rather than the default Atlassian.net. If you want something different consider an addon like Email This Issue (JETI). configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain 

What exactly isn’t working? Aside from the syncing of transitions are you able to do a basic automation to create a linked issue? If you can do this manually you certainly you should be able to automate with built in (some limitations) and certainly with A4J and Scriptrunner. Please provide details of what you have tried…

Ok so you seem to be asking for this... company1@atlassian.net company2@atlassian.net if so this is two completely separate Jira instances. Each requiring separate licenses. you could consider a sing instance like mycompany@atlassian.net and then create separate projects one for each client and simply control access by…

You can export to Or excel all issue in a project as follows: * click on magnifying glass * click on advanced search * in the JQL search bar enter “project = abc” where abc is you project key * click on the export button

What do you mean by organization? While Jira Service Desk has the. Inception of organizations Jira software does not AFAIK. 

For any filters add the following .... and assignee = currentuser()...

Hi Kari, so it may be that in fact you have switched back. There was (is?) a known bug where the reminder to switch back falsely continues to display. Can you verify that you are indeed not logged in as yourself after switching?

Epic names should remain unchanged.

My next guess would be that the admin has not set it up to allow others (you) to create such projects. It is not uncommon to only allow NG project creation. Check to see if the system admin can create JSD projects.

That article is for Server. I wasn’t even aware you could do so there. You cannot do this in cloud. Now one thing you could do, but I certainly would not recommend, is to create 999 dummy and your first real issue then delete the firs 999.

There isn’t any way to query on the ends date of a sprint and subsequently no way to have an email reminder. With that said you can use the sprint health gadget to visualize this. Moreover, sprints are typically so intertwined with how teams work the end date should be quite obvious. If you are doing daily sprints that…

i can't answer with any official word since I don't work for Atlassian. I had heard this would be in Q1 or very shortly thereafter. Sort of expected it might be part of the Summit announcement but just a guess.

generally it is preferred to install JSD on your current JSW instance but not required. If you have not really begun using the new JSD instance then I recommend simply adding JSD to your current JSW. You can use the same license key.

No problem. To be clear I don’t work for Atlassian. I’m a user like yourself. Most of the folks in the Community fall into that category. This is why I suggested the support link. But when you are on starter license the support link simply redirects you to the Community.