Nic Brough -Adaptavist- Expert

I'm with you on that. It's one of the reasons I say that team-managed projects are not ready for "the enterprise" or even just cross-project working. They're self-contained and linking to Epics outside them is pretty much pointless. Company-managed projects have it right - an Epic spans every piece of work it needs to,…

Hey everyone, I've been in the Atlassian ecosystem for a while now, so a lot of the audience here are thinking/feeling "Oh no, not again", but I realised I've been in this group (and contributing a bit) for ages, seeing new people introduce themselves a lot and not done it myself, which I think is a bit rude. So: I was…

Welcome to the Atlassian Community! There is a whole load of complexity that using SSL adds to running web services, but it absolutely should be done for most sites (and far too many sites don't use it when they really should). Anyway, you've got a new certificate that needs to go into your service and you've tried to…

Welcome to the Atlassian Community! You will need to talk to the administrators of the site. We, the community, can't help you - we have less access to it than you do!

It's hard to use an issue tracker to track issues when you don't have a status to do the tracking with!

I am not clear on the exact problem - are your issues missing, or their story points, or do the existing story points add up to 21? Where does the 55 come from?

Welcome to the Atlassian Community! I'm afraid you are probably in the wrong place. "OPMC Hub Staff" probably means nothing to most, if not all, of the people here working with Atlassian stuff. Is it based on an Atlassian system?

It's not quite that. SLA’s * SLAs are set up for a service desk, which represents a group of work items for a team to work together on dealing with the incoming requests and issues. A Jira service desk is a project * You could set up SLAs in a single project based on the customer - SLAs are based on searches * You are…

@Yatish Madhav has already explored most of what I was going to say, but I wanted to add a general usage point. In Service Desk projects, your Agents are not really expected to be going off to find issues with arbitrary searches, they're expected to be working on the next most important thing they can, which is determined…

You'll need to get one of the scripting/automation tools to do this. But I wouldn't bother, an email reminder of what people are supposed to be doing as part of their work is pointless. If they're not using Jira, it's probably because they don't need to. An email isn't going to change that. "Use tool X on a regular basis"…

Welcome to the Atlassian Community! It sounds to me like you have two different projects that need two different sets of fields to be used for their issues. My guess is that they are company-managed projects (you can check by going into any part of the project and looking towards the bottom of the left-hand side bar when…

You've got a validator that is checking the data on the issue and not letting you proceed because it's not valid. You will need to talk to your RM Team or Jira admins (we're not them, we're a community of people here to talk Atlassian stuff - we know less about your specific Jira's set up than you do)

Are you talking about a specific space, or the whole of Confluence?

First, look at the board filter(s). Go to board configuration -> general and read off the definition of the filters there. For a Scrum board, it's just the board filter, but for a Kanban board, you'll also want to read the "sub filter" Do your "missing" issues match the board filter? (And if a Kanban, do they also match…

The two project types are very different in their implementations, and no, you've not missed anything. It's more complex for company managed projects because they are more powerful. The boards (and hence backlogs) can contain many issue types from many different projects and in order to provide that drop-down, they would…

Ahh, I see, you've not explained the context in that you're asking about sending results during a Bitbucket pipeline build. I'm not sure if that can be done directly in the yaml definition, but I'm sure you could write a script for the pipeline yaml to call, one that sends the email from the command line.

You get that in the response to get the issue by default. Have a look at the sample response in https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get

You said "I have added resolution to all steps (create, edit, view) ", which reads as you entering a resolution when you create the issue.

I'm sorry, I should have explained my thinking there. Reading the original question: "our reporter and all watchers only receive notifications for the parent (User Story) when it is updated but when a sub task under the the user story is updated, no notifications are received" I suspect the people who are not getting…

That's why I said "the project is irrelevant". If you're not deleting the issue, the link won't be affected.

Welcome to the Atlassian Community! Team managed projects are completely the wrong answer for this - they don't have powerful permissions, they don't do things cross-project (they're local siloes, not suitable for collaboration outside the team), they don't have security schemes, and they don't do the hierarchy you will…

If you delete the issue at one end of an issue link, the link is deleted as well - they can't exist without both issues being there. The project is an irrelevance to this. In other words, in your question 4, the answer is "nothing" because there won't be anything to click on.

You can add the due date to the sub-task display in the "advanced" section of "general administration". But this only works for company-managed projects in the old issue view.

I suspect you'll find the people missing emails are not watchers.

Nope. I'm not Atlassian support. Nor am I an Atlassian. You're currently asking to do this on an unsupported system. You'll need to upgrade it to an supported system and then raise a support request with Atlassian.

I'm sorry, but repeating the phrase that I am questioning the meaning of does not explain it. What is "update new user with existing user"? What would it actually do?

It's clearly not for upgrades - the upgrade process changes the shape of the database, and that's not happening when you swap 9 in over 8. You're right that Atlassian have not accurately documented this failure.

You said you are resolving issues as they are created. That's broken data.

Correct, it has not changed. But the Agents can do some configuration of the portals and project within it.

Ok, so over the REST API, but what is "current issue of project ID"? As I asked before, is it a search for issues in a project?