Comments
-
Yes, you're right, it has to be tied to an issue. Tempo is working within the framework Jira provides. Jira, at its heart, is an issue tracker, which means an issue is the absolute focus of what it does. Because of that focus, there's simply nowhere else to really put other stuff. You have instinctively hit on the approach…
-
This is something I raised at https://jira.atlassian.com/browse/COMMUNITY-59 ages ago, and is still in progress, although the focus is on improving the filters rather than documenting them for us. Some of the spam-weighting rules are clear - similar or identical posts in several places, short posts with no real content,…
-
The new UI is unlikely to make it to Jira Server until (and this is a 3rd hand rumour, so don't quote me) the next US Summit.
-
The boards are a view of underlying issues. A change made via a single board affects the issue, so the change will be seen on other places that are showing the same issue.
-
That suggests your add-on doesn't actually implement anything. Check the add-on definition file to make sure it tells Jira that there really is a gadget there.
-
Is there a comment option in the "more" dropdown? Are you sure Lindsay has "create comment" permission? Do other people get to comment on the issue? Could there be a workflow property on "in progress" modifying the permission?
-
Have a re-read of the documentation and you'll see you are using it in completely the wrong place. It's a JQL function.
-
Is the priority on screen and being filled in? What errors are there in the logs?
-
Ohh, that's not going to be nice. A stack overflow error means Java ran out of memory space. This is not a case of giving it more memory though, the error is most likely to be caused by recursion - code calling itself inside itself, and increasing memory just means it'll crash a little bit later. I think this is one that…
-
I'm a bit stuck, because this is not happening in the systems I'm looking at. That tells us someone has configured something in your system to do it. Yes, there are increasing numbers of lines in that table in my other systems, but there's no pattern of increasing load or anything else causing a problem. That makes me…
-
No, there's no "pass". Boards do not contain issues, boards are a VIEW of issues. If you want a card to appear on a board, you need to make it match the filter for that board. If you want it to stop appearing on a board, then change it so that it no longer matches the filter. Imagine a very simple case: * Board 1 : Project…
-
Add-ons are blocks of code compiled into plugins that you deploy to the service via "manage add-ons", they're not things you just configure.
-
Can you read the log to tell us what the error is in there?
-
There are two ways to do this. Write some code which reads all the filters in the system and works out if the issue matches any of them Write some code which runs each filter (probably with a prepended "key = x" clause) and see which ones return a single result.
-
You can write add-ons that will create new panels, but re-ordering will require (minor) hacking of the core code (re-weighting the panels to be drawn in a different order)
-
The attachments panel will disappear if you turn off attachments. I think you can get rid of Description if you make the Description field hidden for the project/issue type, and I have a feeling disabling the activity stream system add-on will hide the activity panel. But you probably don't really want to do any of those…
-
There's nothing you can do about this without hacking the core of Jira, or using something that implements your javascript properly (doing it in the announcements banner or field descriptions is a guaranteed failure). The correct answer here is "stop hiding the fields if you need them". Trust your users to get it right. If…
-
Technically, yes, but there are other options. A port can only be used by one service at a time. So if you run Confluence and Jira on the same server, they will need two different ports to run them on (Service Desk runs inside Jira, it's not a separate service) When you do that, you end up with urls with ports buried in…
-
Without knowing what you've tried, it's quite likely someone will give you the code you've already used. Could you tell us what you've tried?
-
The Excel export was not Excel either, it was XML that says "hey, I'm a spreadsheet". In theory, I understand why Atlassian has replaced Excel with CSV - CSV was the single most demanded form of export for years, and should make a perfectly good replacement for Excel as spreadsheets can read it just as well as the XML.…
-
Those are not fields, they are the titles of the panels that are wrapped around groups of fields or other data.
-
What add-on is providing it though?
-
This usually means the client is not getting the javascript and css from the server, which is usually a badly configured proxy or Tomcat server. Could you try tracing the files it should be fetching from the server and see what the error is if you try to fetch it in a browser?
-
Only if auditing was enabled at the time of project creation.
-
The comment on it already states the current standing, that's not changed. But it has not been closed.
-
Your workflow is setting a resolution when it goes into "done", but not clearing it when moving back. You need to look at the transitions out of "done" and add a post-function to "set issue field: resolution to <none>"
-
I don't think you can do this on Cloud, as you'll need some code that can check the current user's assigned issue list and then block a transition if it is inappropriate. Cloud does not support conditions like that yet.
-
Technically, you don't "report on custom fields", you report on issues and choose to focus on particular fields. So, a report on a drop-down is an easy one. Run a filter for the issues you want to report on ("Field x is not empty" for example), and then save it. Go to dashboards, create a new one, or pick an existing one…
-
Yes, assigning an issue is an "edit" as well as an assign function.
-
It sounds like you are trying to restore a whole system over your Cloud system, rather than importing a project. Cloud does not have a project import that takes a project. You need to set up the Cloud system with an empty project, configure it correctly, then import the issues.