nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Somehow when creating an issue, it creates into another project?

Josh McCloud

We have checked the emails created for each project, but somehow when we create an issue in one project it is logging to the other project? How can this be when there is no affiliation in email notifications and Adirectory? Can someone please help us on this. Thank you!

Accepted answers

All comments

Nic Brough -Adaptavist-

How are you creating the issues? In the UI, or by email? Or something else?

Josh McCloud

when creating within the project it will go to correct project, but when emailing outside of jira, it is sending to another project and not the correct one.. we have removed the affiliation in adir. and still is sending to wrong project.. this one has us flustered to we have tried everything.. any help be appreciated.

Nic Brough -Adaptavist-

Right, so it's the email that is failing.

Look at how the email service is configured - you probably have the wrong project set up in there. This has nothing to do with adirectory (whatever that may be) or notifications, it's in the handler setup.

Josh McCloud

yes we have checked that as well.. each service pop email setup is setup correctly.

Nic Brough -Adaptavist-

Not the pop side, that must be ok for you to be processing emails. What about the handler - what exactly is the configuration of the handler? In fact, ALL of them, if you have more than one.

Josh McCloud

all our services are set correctly to: create or comment handler, as i said this just started happening just a couple days ago, only with the 2 projects somehow.. this is really becoming a pain.

Josh McCloud

We have resolved issue.

Nic Brough -Adaptavist-

I am assuming that the lack of explanation here means that your resolution was because you finally read the configuration of the handler, and that told you what you were missing.

Nic Brough -Adaptavist-

Ahh, so looking at the handler told you that you had an odd email address then, and that led you to the duplicate. I see.

Josh McCloud

incorrect, was issue with an email having an alias with or jira support email. resolved.

Josh McCloud

incorrect, issue was with email alias with jira support . closed

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud