Comments
-
Then there must be something else holding the files open. Annoyingly, Windows is bad at this sort of thing and probably won't tell you what it is It might still be the service - sometimes they do not stop properly, but remain running. Check the task manager to see if any java processes are running. Otherwise you'll need to…
-
Could you explain what you mean by ACE? (Here, it usually means Atlassian Community Event, which isn't something you run on a computer)
-
Not quite, projects are created in Jira, not Software or Service Desk. They are of a type of Core, Service Desk or Software, changing their behaviour. But, yes, Request arrives via a Service Desk project (and part of the request is the underlying issue), your Agents either handle it, or decide that development effort is…
-
Currently, the hierarchy in Jira is Epic, Story, Sub-task (although you can have many types of issue at the levels of story and sub-task) So, whilst you could go off and create features, they'll just behave the same as stories, not as a separate layer in the hierarchy. Jira's Epics are probably mis-named, as, if you were…
-
I'd reach for https://marketplace.atlassian.com/apps/23337/elements-connect-external-data-fields?hosting=cloud&tab=overview to do this without doing any coding!
-
I am sorry, I missed the WBS Gantt chart. I think that is injecting the fields for its dependencies.
-
I don't think there's a way to do that - the sub-tasks are part of their parent issue, not independent items, so they get done within their parent.
-
It's not happening in the application. The error is from the database telling the application it can't handle the data the application has asked it to store.
-
Yes, that's correct, sub-task estimates are not part of the sprint.
-
I'd question why you think you want to do that - I can't think of a good reason to attach a file to many comments, and I suspect Atlassian think the same, and have hence never made it able to do it (other than when you're not really using Jira properly)
-
The model is not simple, so it's probably worth explaining it. Underlying all of this is the idea that there is a pile of issues which represent "something someone needs to do something about". Jira (technically now called Jira Core, and sometimes referred to as the Jira "platform") is an issue tracker. It organises issues…
-
Sort of. See https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html
-
Why are you double licencing here? You have one Jira install, you licence it for (say) 100 Developers and 5 Service Desk Agents. (The agents may need a developer licence if they're going to be part time developers and need access to the boards, but that's not double licencing, just recognising that some people need access…
-
No, the introduction gadget has one set of text. You could look at the "dashboard text" gadget (it's probably disabled though as it can be abused or messed up by people and most Jira admins don't want to have to clean up the mess it can make)
-
Distribution lists are not email inboxes, so they can't be used like this. Best you can do is have a dummy user/email who is a member of the list, so that they get emailed when the list is poked.
-
You can now swap the collation of MySQL to one that supports the emojis.
-
It's almost "a sprint belongs to a board forever" - the problem here is that you have had issues in that sprint, and that means they need to be reported on as such, so as long as you have issues that were part of a sprint for a board, then yes. You'd need some way to clear out the historical sprint on those issues (I'm not…
-
This is almost a pre-Cloud question, but at the moment, I'm not really seeing Cloud support scripted project creation. The REST APIs are not there yet.
-
Look to the two "custom field" options in the security levels.
-
What type of field is the "resolution text"?
-
We're not support, we have less access to your system than you do. I am guessing here that other people are getting email from Jira, and Laura is not. If this is the case, then the problem is * Laura is not configured to get notifications - check the project settings and notifications * Laura is the one making the changes…
-
There's no update, there's not going to be any change to break global ranking.
-
You will need to read the application log to see why it is failing. Have a look at <jira home>/log/atlassian-jira.log first. If that is empty or just stops without a pile of errors, then look to <jira install>/logs/catalina.out
-
No, there's no way to do this for the same system. The system is enabled at one level or the other, it's not done by user.
-
Sorry for the delay in responding. There is an app that does something like this, which is why I asked, but you haven't got it. That suggests that these two blocks are simply custom fields that your admins have added to the project/issue type. Your admins can remove them.
-
As you can't run build agents on Salesforce Cloud, I have no idea what this has to do with your problem. As I said, you'll need to configure your build such that the build agent has an environment that includes the scripts it needs
-
Yes and no. That's the right application, but note the "cloud" selector at the right - that means the licence is handled differently to what you're seeing because it's a Cloud system.
-
Yes, that's what the collaborative editor does. Everyone editing the page can see the others edits happening, similar to sharing a google doc.
-
For a space, go to space settings -> content tools -> attachments There's no Cloud solution for "all attachments in confluence" that I've found.
-
You would need to rewrite the screens and code that renders the backlog, and bear in mind that this would destroy your ability to rank the issues.