Comments
-
A screen is used in JIRA to put a set of fields in front of a user as they do certain things. A listener is a background function that catches events and acts upon them. It's nonsense to "call a screen from a listener". The listener is not on the front-end.
-
Could you explain what this has to do with an Altassian application?
-
I can't think of a way to do this without hacking core code in JIRA. You can set permissions to block the entry of work-logs, and because of that, you can do it on status with workflow properties, and you can do things in transitions, but I can't think of a way to do it based on custom fields.
-
You'll need to write some code to "download" this information en-masse. At the very least, an extract to expose it on issues so that you can export it.
-
By "format", you mean "location"
-
You'll need to write some code to do that.
-
You can either embed some javascript in your code, or modify the header of the page in the html your code generates. However, in both cases, don't. It loads the server and it's bad for the user experience. Ideally, you should only reload the part of the page you need using AJAX.There is probably a much better way to do…
-
Ah, sorry, I forgot, JIRA 4 doesn't have its own JRE. The JAVA_HOME in your script is wrong, which might explain some of it. First run ls -l /usr/bin/java I expect it will say something like java -> /usr/local/java_1.6/bin/java You need to set the JAVA_HOME to be the path to the complete java installation, the directory…
-
No, there's no way to add additional fields to versions. Even the server version is lacking in add-ons that do it from what I can find, and there's definitely nothing for Cloud. There are add-ons which can help you with associated data though, Portfolio, Big Picture and Tempo all have some things that help with version…
-
Yes, that's the con for option 2 - a user would only see the request, not the issue behind it. However, if the agents were to add the original user as a participant as well, they'd at least be able to see and comment on the main JIRA issue behind the request.
-
Not a problem. If you go to /apps/jira/bin and run startup.sh manually, then it should either error, or try to start JIRA and write to the catalina.out file.
-
Look at the permission scheme for all your projects. You will need to ensure that your user only matches the "create issue" permission in that one project.
-
Can't be done without add-ons. You need a new field type (requires an add-on) or something that ties fields together to make them interactive (parts of this is possible with injected javascript, but you'll need an add-on to make it work properly)
-
Depends on how you're doing Change Management. If your changes are just JIRA issues and not being done in Service Desk projects, then no, you don't need SD agent licences for your Software users to create them. If your changes must go in a Service Desk project, then either 1. Yes, you will need 2000 agents if you want to…
-
In a change management system, a user should be able to say "actually, I don't need this". Deleting a record destroys the information that someone else may have worked on it or started to make changes and so-on. So, no, just because you can create something does not mean you should be able to destroy it. In some cases,…
-
Ok, if there's nothing going into the <jira home>/logs, then the Tomcat is not getting as far as starting the application. So, we need to look into <jira installation>/log directory for "catalina.out" and look at the end of that file to see why it's not starting.
-
I assume that means some emails are arriving with some people, but not others? Check who the notification scheme says the events should be notifying.
-
It doesn't "copy" the change, it shows it. When you enable parallel sprints (and in some other cases), the boards will show you the sprints going on. When you change sprint 1, both boards show the new data.
-
No. The user is outside a space at this point, so the system has no context to know what the theme is. It has to use the global theme.
-
Sorry, I didn't notice the directory you've used. Could you try re-reading the comments above instead of randomly guessing where the file goes?
-
Have a closer look at the bug you've found - it states what version the bug was fixed in.
-
Set up the project as a Service Desk project, and then create the Agile boards you need from that project. While Service Desk projects need to be flagged as Service Desk to make the portals work, Software functions simply need to be told to look at an existing project. You will run into one problem with doing this though -…
-
Give us a chance! Many of us have things like work, sleep and a life to spend time on.
-
Stefan's solution can work for one project, as you can give that one project a different workflow with that change in it. The doc site for Atlassian is having problems at the moment, Atlassian are investigating.
-
Absolutely not. It's not a field, it's an indicator of where the issue is in its workflow. So an issue will *always* have a status. If you want issues to have a different status after creation, you'll need to automate the transition from the initial status to another. Have a look in the marketplace for the Automation and…
-
>i thought the community was connected to Atlassian It is - it's hosted by them, and some are active here, but it's not "proper" support, it's for us to talk to each other and help out, not provide a support channel.
-
It sounds like your system does not have a "Ready for the bill" status in any of your workflows.
-
What do you mean by "extract"? The data is in the issue history, which you can read.
-
Excel export is done from the issue navigator. Search for some issues, then look for the links
-
Give it a few minutes, and try again. Atlassian are aware of it. We can't help though, unless someone has a copy of the one you need, we're a community of end-users, not Atlassian.