Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! Support is reachable from https://support.atlassian.com/contact Here, we might be able to help if you gave us the context and the error messages.

Automation can fill in a link field, or put links into text fields. Where exactly are you stuck?

This sounds like you want to create defects as sub-tasks on issues, but you have set up defects at the level of issues rather than sub-tasks. You'll need to delete or rename "defect" as an issue type, and add it again at a sub-task type.

You have a user account dedicated for the Dynatrace integration and you can log in as that, but the error messages are very clear - that user does not have permission to do what it is trying to do. You need to give the Dynatrace user permission to log in and update the issues it is trying to amend.

Jira doesn't really have that simple "x points rolled over" reporting as you describe it, because it's not that useful. What would your people learn from "team X tends to over-commit, but they're not improving their process"? It's certainly something you should look at, but an overall report on it across all your teams is…

I can't see a "bug" there, just the (unintuitive for humans, but actually useful) quirk that if you want to see things that do not have a label set at all, you need to ask for it. Try: assignee = currentUser() AND (labels not in (XXX, YYY, ZZZ) or labels is empty) ORDER BY priority DESC, updated DESC

Yes, you write up a story that says where you want to go. Your development team might break this up into bits according to components, skills or even just who might be around this week (your three sub-tasks). You can see all the sub-tasks in a story when you look at the story. Or you could create a load of stories and use…

I'm going to have to pick that apart in pieces: >the scrum team is not just made up of developers. Yep, that's absolutely right. A scrum team is made up of a load of people who need to work on stuff together to get it done. >If I pile everything in the same column it will be hard for the release team to [...] Yes, it will.…

Yes, you have it completely right, the "remaining points" on the "issues not completed" are indeed the same points that are rolled over into the next sprint. In an off-the-shelf scrum process, your team would go into sprint planning, fire up the board and see that their next sprint has some points in it already (rolled…

Welcome to the Atlassian Community! Go to your site admin and shut down / delete all the trial services you have signed up for. Then go to id.atlassian.com, log in with the account you used to create the trials, and find the "delete account" under profile -> account settings -> account preferences

Welcome to the Atlassian Community! Users do not have subscription levels, you can't have some users on Standard and others on Premium - your subscription is Standard or Premium.

Sub tasks do not have sprints, so I'm not exactly sure what your problem is here. Could you explain more please?

Status is changed by transitioning issues through their workflow. See https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-transitions-post for the methods you'll need to use

Stop using the administrators group in project permissions. Admins are admins because they are a member of a group that is flagged in global permissions to grant access to admin rights. It has nothing to do with project permissions, but a lot of people use the admin group in project permissions, and it grants access for…

My guess would be that your colleague's account does not have permission to see some issues that have certain labels on them.

The name you see in the workflow button is the name of the transition, not a status name. Edit the workflow and check that the transition names match up with the target status of the transition (by "match", I mean make them use appropriate language, not just the status names - for example, a transition to the status…

Welcome to the Atlassian Community! Technically, it does not need a service account, it just needs an account that has access to all the services on the operating system that it needs to be able to use to do the job. Most of us use service accounts for running Atlassian services because it keeps things secure and simple,…

Jira is a service - it runs on a machine and you use a client (such as a browser) to connect to, and interact with it. There is no "offline access", you need to connect to the service to use it. You could run a local instance on your machine if you wanted to always have it available (the machine I'm using to write this…

It would be a lovely function to add to the issue navigator, and some other places too!

Welcome to the Atlassian Community! What are you looking for with this "capacity planning"? In general, the velocity can be used as a measure of capacity, as it tells you how much the team has been getting through in each sprint, and hence how much you could expect them to get through. In fact, that is what velocity is for…

You can't hide these apps, they are in use in the project.

I've read all of that, it does not tell us anything that would change or expand upon my explanation.

Welcome to the Atlassian Community! This site here is a place where people using Atlassian stuff get together to talk and ask questions. The email you had was from your organisation's Confluence (Confluence is an Atlassian service), and is intended to invite you to look at what other people in your organisation are writing…

Jira doesn't care where an email address lands, it really does just have a primitive "send to xxx@yyy.zzz" function. If xxx happens to be a list, that's fine, that's up to your email server to send to the list.

The errors you have there are mostly shut-down warnings. Could you show us the errors that are about why the service is stopping? The lines above "stopping launchers" are what we need to see.

Yes, use the field in the issue security scheme.

Yes, this does make a lot of sense. 1. Yes, very much so, that's why labels are useful. 2. Yes, you're right, it is very easy for people to create junk. If you want to stop this, then use a controllable field instead. 3. Ah, now that is technically wrong - to remove a label from circulation, search for it, then delete it…

Because that would totally disable your ability to do any administration, and render your system fixed and unchangable. Why would you want to do that? Could you explain why you are looking to do this? What problem are you trying to solve?

Just a couple of minor clarifications 1) You say "it seems notifications only allow for one email" - actually they don't allow for any emails, they send emails to user accounts (which all have email addresses), and they send to as many as you define in the rule (deduplicating though, so if a user is matched by group,…

Welcome to the Atlassian Community! Could you tell us the symptoms of "cannot download/delete/change files in scratch"? What exactly are you clicking on / typing / using, and what are the error messages?