Comments
-
It hasn't changed since the original answer
-
I thought it might be :-) Attachment handling in Jira is pretty basic, you add them to an issue, that's about it. When we've got complex lists of documents, we put the doc name in the comment, or more normally, write it up in Confluence instead.
-
To answer your title, comments, no, as comments belong to issues, alongside attachments. To answer the body of the question, yes, you attach files to individual issues in Jira.
-
Boards use filters to choose what issues to show. You could have a board based on "updated > -15d", but then you'd be ignoring older issues, it's not something I'd generally recommend for a working board. More of a reporting board. If you're asking for this for an existing working board though, then add a quick-filter for…
-
Because there's something wrong. Have you tried raising it with Cloud support? Also, it's not an Atlassian written application - it's Flapps Inc. At least try reading the support information.
-
The difficulty is that (ABC) v1 is a different version to (DEF) v1, despite having the same name.
-
Best practice is:1. When you are making changes to fields etc, that prompt the admins to get the "please reindex" box, you should re-index as soon as practically possible. So that your users can actually search for your newly changed stuff. I know there are issues with it - you don't want a full re-index during the working…
-
Script or plugin - I've used both in the past to trigger it. However, the desire to do regular re-indexing is usually driven by the index going wrong regularly, which it should not. This is indicative of another problem, and you REALLY should fix that, not plaster over the cracks. That leads me to ask "why do you want to…
-
Ah, beat me to it. I was going to ask if they meant the "status" or the "status category".
-
I'm not sure what "detail" you need here, especially as I don't know what external application you are attaching Jira to here. You need to put in the URL which Jira will send the data to when the webhook is triggered. That's up to your external application.
-
I'm sorry, I don't understand the question.
-
Wrong way around - webhooks are for doing things in other systems when something happens in Jira. Of course, the remote system might be a Jira or other issue tracking system, so your webhook in your Jira could be creating an issue in another system, but you're likely to be using a REST call in that webhook. See…
-
Nah, it's easy to miss - there's so much in Jira, you can't be expected to remember all of it, especially if you're new (and heck, I forget that one for a while on every second client site!) No, it doesn't explain the notification checker - I think that needs rechecking to see if it's reporting accurately - could you…
-
It sounds like you have the "do not email me on my own changes" flag set in your profile. That kills off emails that your activity would normally send to yourself. e.g. if "create" is supposed to go to "assignee and project lead", and you are the project lead, you will get notified of issues created by everyone. Unless you…
-
Conflluence is not a file storage system either. It's good if you import the data and convert it to proper pages, but uploading large binaries is the same for Confluence as JIRA.
-
I'm with Jonas on this - JIRA is not a file storage system. If you have large files, a proper file store and linking is definitely the way to do it.
-
* Code changes * You set a default project * Google "Jira Jelly escalate" * See 3 and modify that to suit * Not really, but some people have had success with printing from browsers * Look in docs for "wiki markup" * Yes, it's a setting * Have different fields and workflow by issue type (workflow schemes, field…
-
Your systems will continue to work. No changes, no data loss, no impact on the users. Except that you'll see a few "unlicenced" reminders in a number of places (most users won't see or notice them, it mainly affects those with administrator rights). You will be able to download and apply security updates. However, you will…
-
It's ok, I often misunderstand questions, so I ask.Yes, JIRA provides hooks for this. The obvious method is to use the REST interface in your code - when you need an issue, your application calls the create-jira-issue REST function. But that does mean you are doing all the work.The other option you might want to check…
-
JIRA provides a full issue tracking UI to answer your first question, but I'm unclear on what you are trying to achieve. It sounds like you want to show issues in JIRA in your own application. Is that the case?
-
You'll need to find or write an add-on that can provide such a field.
-
In later versions of JIRA, you can remove it from the default scheme later. Most admins just don't use the default scheme though, then it doesn't matter.
-
I know of several places that have adapted their Jira systems to match ITILv3, although I can't say they were using it for every single thing ITIL covers. They needed varying plugins and a bit of work on Jira configuration, but a couple of them managed without any plugins at all (one by saying "this bit of ITIL is wrong…
-
Sorry, I wasn't too clear there - the strikeout happens if you put *any* resolution into the field. It doesn't matter what the value it. Jira treats that as meaning "no more work needs doing", so the issue is effectively closed as far as it is concerned, even if the status does not match. If you genuinely have "incomplete"…
-
You don't. You should not set a resolution if you don't want the issue to be resolved.
-
You can't. They will be struck out when they are resolved (i.e. a resolution is set).
-
Yup. Sorry, I keep forgetting it's called "search template" in later versions
-
When you click "add new field" and choose a type, Jira asks you about a name for it, what searcher to use and the project/issue types to apply it to. That's where you select a searcher. Go to "edit" on the field to check this. Also, when you say "select list", is that *exactly* what both the working and broken fields show…
-
What type of custom field is it (and the others that do work)? What "searcher" did you select when you created it? Have you re-indexed?
-
Well, it did need you to explain what you were trying to do, so I could see what the real problem was, rather than just your "delay" solution. I'm not sure what you mean by "thread" to implement the logic. And do you mean for the solution I gave, or your delay one? If it's the delay, then no, I still wouldn't do that on…