Nic Brough -Adaptavist- Expert

Yep, you might want a quick look at https://community.atlassian.com/t5/Jira-questions/to-automatically-replenish-Duedate-by-Severity-when-creating-an/qaq-p/1990926 - it's got more complex (date) calculations in it as an example, you should be able to simplify it down quite easily.

You will need to set up shared authentication between Jira and AWS (probably by tokens you can use in the webhooks), but we can't help you with that without knowing how you are doing users in your Jira, or how you are doing users or remote access to your AWS systems.

Welcome to the Atlassian Community! I think you have asked this in the wrong place. I suspect your application/service is using Jira to do issue tracking, and you have clicked on "help with Jira" instead of "help with the application/service". You probably want to contact the admins of your application or service.

The usage per page is when a page uses a macro provided by an app. That's actually available as a report in the UI, as well as the migration assistant. Usage per user is partly done by analytics, which is stored in the database, but is absolutely not complete, as it doesn't track all the ways apps can be used.

No, there's no way to have time logged in one project appear in another. I'd want to look at a different approach, instead of looking at the project to gather together time, identify the issues where time matters to a client with something else. Either a flat simple field (stick the client's name on every issue in a label…

Do they have open sub-tasks - that's the other thing the sprint checks. By definition, if an issue has open sub-tasks, it can't be done, parts of it are not done.

They'll respond on the issue when they've got something useful to say. At the moment, they're having a major incident, so support staff are trying to fix things for everyone, and lower level support calls are not a priority (especially as they're getting a lot related to the incident). Follow it…

Welcome to the Atlassian Community! You can always recreate and export your backlog in the issue navigator (run a search for "your board filter and status not in (any status in the last column on the board"). Make sure you add the sprint field to the display so that you can see issues already allocated into current or…

What assistance do you expect them to provide here? They have an incident that affects many systems, they are working on fixing it. If they take time out just to give you a copy of the data or other "assistance", they're diverting resource away from fixing it.

I think what you're trying to say here is that you want a field to be filled in when you move an issue into the status called "On Hold" To do that, put a validator on the transition from <wherever> to On hold, one that checks that the internal assignee field is filled.

Attachments are not kept in the database! They're simple copies of the files that were uploaded, renamed so Jira can version them, but just plain copies. They live on the file system of the server, under <Jira home>/attachments, or <Jira home>/shared/attachments depending on how your server was originally set up. A backup…

If you have scripting or automation tools, you could * Create a validator on the create transition to check it's been entered correctly * Create a function that overwrites the summary, Both of these are a bad idea, one makes it hard for people to enter issues, the other destroys data they deliberately put on the issue. It…

Hi James, I'm not an Atlassian, just a Community member (an old one, admittedly), I've got no more access to the support systems than your do! Your support request should have emailed you a reference at least. If Atlassian support thinks it is worth a call of some sort, you can expect a comment and email about it on your…

Welcome to the Atlassian Community! Well, ouch, to begin with - the whole point of a sprint is that you are only supposed to take in work you can complete in the sprint. If you're moving things from sprint to sprint regularly, you're failing - your estimates are wrong, or you're over-committing, or you're not doing…

I think your approach to the data is exactly right - a board that shows your main project and then draws in other stuff that might need your team to see it. But you don't mention how you are using boards. You've only got one listed here, and it's usually best to think of a board as being a team. Do Team B and team C have…

Welcome to the Atlassian Community! You've not told us what level of account you are on (which might be important because most levels don't have email or telephone support) Did you raise the issue at https://support.atlassian.com/contact ? Even when there's telephone support, they'll need a record there to get the…

Atlassian had an incident, you can see progress at https://status.atlassian.com/ 

There are four levels of administrators in Jira * System admins - can change every aspect of the installation. Only Atlassian have this right on Cloud systems, customers will never get this. * Site Admins - only exist for Cloud sites, and they administrate the whole site, not just Jira. They don't even have to be…

There is no way around it, you need IT to give them a usable email address.

Welcome to the Atlassian Community! There's no way to do this, Jira is supposed to be tracking all changes in its issues. All you can really do is secure the entire issue away from people who should not be privy to the sensitive stuff in the history.

Well, clunkiness aside (I'd recommend changing your process so that there's no cloning happening at all), you can still do it with the method I described.

I'd agree there's some problematic thinking here, but it's not on the Confluence side. The activity stream will not expose protected information if you've secured it correctly.

Depending on what your javascript is trying to do, you might be able to add it into the announcement banner, but that is a global action. It would be a lot better to use an app intended to get the effects you are trying to do in your js (even if that means simply putting your js in an app)

I'm sorry, but repeating the statement we are questioning does not help. Try explaining what you mean by "hit" for a start. What is your Jira doing when it "hits" AWS?

You would have to rewrite the software to do this.

There is no way to do this - issues live in projects, and you can't define an issue as belonging to more than one project. (Imagine what a mess all the configuration would be, given that it all is done at the project level)

The resource must be incorrectly defined in the apps definition file, or in the wrong place.

Boards are intended to represent a team's work, they're not intended for multiple teams (other than for other teams to see what a specific team is working on and how it is going). There's no problem with what you're doing here, but you need to re-think your not-scrum process if you want it to be shown to you usefully in a…

Yes, you did, you stated that it is something that needs to be done by another team from the front-end story.

But you've decided it is a story in its own right.