Comments
-
The new forum system we've got here has lead to a lot of us simply not seeing posts. I've only just caught this one, so I'll give it a shot: Yes, form data should be quite easy to send over. I'd translate it into your desired JIRA data, then output it as JSON and post it over the REST interface into JIRA. The email…
-
No, the link created is the "documentation" that the issue was cloned. You can see "links" in the issue navigator (search results), which would show up the clone link.
-
No, you don't. Seriously, that is NOT going to "make reports easy". To perform a full search for JIRA issues matching something, you could have to join the main issue table up to 30 times, and via multi-layered joins. Even a search for a simple custom field is 3 or 4 joins, depending on the type. SQL is the worst way to do…
-
No, you'd have to hack core code to do that. I'm not sure it's a good idea either, as your users would be questioning the different information in the mails if they talk to eath other.
-
Adding files into it is not going to have any effect on its own. How does the system know you want it to use a file you've just dropped into it somewhere? If you want to modify the login.jsp, you are going to either need to tell the code where your new file is, or modify the file it is currently using.
-
That's not how JQL works, it is not a list of issues, it is a filter. In one sense, there's an easy answer to the question. Issues are never "added" because it's not a list, so there's no need to send any notifications. What you need to do is run the filter regularly, with an extra clause that says "since the last time it…
-
There's no additonal cost in linking JIRA to Bitbucket.
-
That's actually up to you. The links are configurable and you can name links however you want. "Has to be done after" is a name one of your adminstrators has added, so I'd suggest you ask them or your colleauges how they intend it to be used.
-
I'm not sure Atlassian can do a lot about the networks between the US and India. They currently only have data centres in the US, although they are looking into getting another one in Ireland. However, they might be able to do something - you'll need to raise this with https://support.atlassian.com to get them to look at…
-
Excellent, glad it's all working now! My squad is currently working on several merges and finding duplicate email addresses are shared are great "fun" parts of the process. We dummy them out quite quickly, but we still forget regularly, and have that "oh bother, we forgot the emails didn't we?" head-slapping moment.
-
It's quite common to do that. It does make sense, and it does work, but it usually needs a bit of explaining to users as some will ask why their cards vanish. The trick is to have a board filter that says something like "and resolution is empty". This means you still have a "done" column to drop your cards into when…
-
No. It's not often I get so blunt about these conversations, but Your teams are wrong. It's not an opinon or a point of view, they're just wrong. They have put you in a place where you have broken data which contradicts itself. You need to work out why they want this, and that should tell you where they got their thinking…
-
Trello or JIRA?
-
You can do this by editing the workflow. Find the transition that takes the issue from the "in progress" column to the "done" column and add a "transition screen" to it. Put the fields you want to ask the user about on that screen.
-
You need to edit the workflows and remove the status you don't want from them.
-
The three categories are pretty much hard-coded, so you'd need to go digging into the core of JIRA to add one. I'd check your board filters carefully, as you say your issues "disappear from the column view", it suggests your filters are hiding them from the board.
-
It's what Ann says - you need to remove the workflows that use it from active use, and then you'll be able to delete them.
-
Yes, you can, it's all about the workflow. The three categories really are just logical groupings of status that doesn't do much in itself.
-
Reading the JIRA database is usually a terrible way to do anything, as it's "designed" to be a datastore for JIRA, not any form or reporting tool. Could you explain what you are trying to achieve? As there is a better way to do it than using the database. ----- But, to answer the technical part, start with the JiraIssue…
-
It's not a bug, but it's not intuitive for humans. When you ask about the values of contents of a field, you need to look at the content first. The question "is the colour field red?" works ok when your field has red in it, or green, or has no value at all. But when you ask "is the colour field not red?", you'll get what…
-
This does seem to happen a lot, especially when you're coming from MS-SQL or MySQL databases. First step is to try the cleaner - see https://confluence.atlassian.com/jira/removing-invalid-characters-from-xml-backups-12079.html
-
My guess is that it's not set up for anonymous users, so it's ignoring people who don't have accounts yet. Have a look through https://confluence.atlassian.com/servicedeskcloud/receiving-requests-by-email-747602718.html to see how to configure it all in full.
-
You can shut it down in your my.atlassian account, or if you're struggling, ask support over at https://support.atlassian.com We're a community of end users, we have less access to your Cloud account than you do.
-
Sorry, I meant "site administrators"
-
You will need a bit of code to do this, but there are plenty of add-ons in the marketplace that can add the functions for you.
-
This can happen when an add-on that provides post-functions is broken, but the first place to look is really the log file to see if there are errors in there when this screen is rendered.
-
You need to add more users to the groups that allow administration. You can't change the system administrator, it's an account for Atlassian to support you with, not a user account.
-
It sounds like it, yes. If you want to create requests from emails, you need to send the email to a mail box JIRA can read (and delete from by the way)
-
Gmail is not an Atlassian application. The tasks are not going into gmail, I wanted to know where they were going. You actually want to talk about JIRA Service Desk here. What that box is asking for is the gmail address you want to use to collect issues from. People will email that address, mails go into a mailbox, Jira…
-
Which application are the tasks going to go into?