Comments
-
Velocity is calculated on all issues on the board that are at the level of the story (not epics or sub-tasks). It does not care if they are called bugs, tasks, penguins, it just looks at all the standard issue types and looks for the field you are using for the estimation statistic.
-
Break up the two clauses - which one of the summary or status is failing? (or both?)
-
Tempo is for time tracking, not user data or boards.
-
You need to amend the script so that it does not try to run if the resolution date field is empty. If you can share the script with us, we can probably help you correct it.
-
Ok, the easier route is the one described in the document you mentioned originally. I'm not sure what lead you to partially set up SSL on the Tomcat end and then start looking at the wrong connectors, but it's not needed for the easier route, so remove all of that, reverting back to a plain http Confluence installation.…
-
Those are two totally different connectors and they're trying to do different things - one has Tomcat encryption, the other is set for no encryption and running via a proxy. The second one is not expecting Tomcat to be encrypted and hence getting the wrong headers and falling over. You need to decide what you're trying to…
-
It's not crazy at all - those sprints need to be seen and used.
-
It might not be the network, it might be the client machine (i.e. the browser). But whatever it is, it's not a Jira problem, it's that your machine is not resolving the url to the right place and the browser is taking it as you wanting to search instead of to the url. It's happening before Jira is reached.
-
What does the issue history say for the issues that are re-opened? What user is doing it? My guess though - you've got an "automation" re-opening them incorrectly. I'd read through the automations in the project carefully!
-
What does "it's not working" mean? What are the symptoms, what are you doing, what are you getting and what do you expect?
-
I'm afraid no easy ones - there's a whole load of issues logged with Atlassian about improving the way the organisation field is handled. I've heard people use ScriptRunner to effectively copy the field to a proper custom field that then can be used for stuff sanely, but it's a bit of a bodge because the organisation is…
-
Jira has no concept of your "team board" - a board is a board. There's no way to know what boards you might consider to be part of the bigger board. Even if there were, there's also no user -> board link. Boards are shared with a project or group for the purpose of usage, but that probably is not what you are looking for,…
-
Possibly - you'll need to explain what MTTR is (I can think of eleven different things it might mean, nine of which might well apply to service desk) and what you want from it.
-
This is effectively the same question as https://community.atlassian.com/t5/Jira-questions/Is-there-any-way-to-get-current-sprint-details-for-a-user-using/qaq-p/901901 which has more clear information on it.
-
Ah, the organisation field is a special field for grouping customers together in the Service Desk. It's locked because changing its config will break JSD, so you don't want to change it! This field also has weaknesses in its implementation - it's not really an issue field and sorting, dashboard display and exports don't…
-
That does not look like a full error to me, there's no context around it to tell us what is going wrong, just a chunk of data that's part of an error. I'm afraid we can't help you without the full error.
-
Could you explain what this has to do with Confluence?
-
Yes, the context path for Confluence is irrelevant to Synchrony
-
I do not think this has anything to do with Confluence (as there's no video background, no tabs, and no such thing as "pro"), and you've landed in the wrong place. Probably the docs are written in Confluence and you've clicked on the "help with confluence" link in the footer. If it does relate to Confluence, could you…
-
There's a lot of stuff you can get from the REST API, but I think you need to think about what you're asking and form what you really want more clearly. Sprints and users do not have a relationship (a sprint does not belong to a user, and users are not in sprints). So "current sprint details for a user" does not make…
-
What type of field is it?
-
There is no export project, you have to take a full backup as xml. Import is in the import menu in the admin section.
-
What you are calling "cleaning" is really "removing functions that people using your system want or need" >It is suggest able to do that ? Sometimes. It depends on the usage and how it is applied. A lot of my points are project level stuff where you might or might not want to do it. For example; some projects might not…
-
Yep. Your system is not able to resolve the JIRA server address.
-
Remove the options via permissions or add-on restrictions * Log work - remove the permission for the user to log work * Agile & rank - remove the user's Software access * Attach * io.deaw - remove the attachment permissions * Watch - turn off watching * Sub-tasks - remove all sub-tasks from the issue type scheme * Branch -…
-
Mostly, yes, but it's not quite that narrow. The query for the board can draw in issue that *could* match but do not yet do so. Let's say you have the following * A developer called Dave who can be assigned issues in any project * Board 1: Project = X * Board 2: Assignee = Dave or Project = Y Board 1 will include sprints…
-
No apology is needed on your side - I'm happy that you found a thread that looked related and you asked. This conversation is messy and unclear (unintentionally of course), and it's better that you asked and got a pointer, than stayed quiet and got nothing. On my side, an apology was the right thing - my accidentally…
-
I think you've done almost everything you reasonably can. Your two steps on reading the notes and checking the auto-correct are pretty much right. In an ideal world, your idea about the third step is exactly what you should do. Get a test system and run through every script to check it does what you expect. Personally,…
-
If you disable time-tracking, you will not be able to use time estimates and worklogs to track the time people log, which means * Yes, it impacts sprint if you use time as the estimation statistic * Yes, you will not be able to tell how long people spend on an issue, because you have turned off the data used for tracking…
-
This looks like you are following instructions for Cloud, but while working on a Server installation. Can you tell us if you are on Cloud or Server? (The easy check - all Cloud systems run on https://<something>.atlassian.net - if it does not include atlassian.net, it is Server)