Comments
-
Ok, but you did say " I would like to save the asset information directly in SQL Database instead of the file system" Assets live in the Jira database, and Assets Discovery is built to work with that database, it is not intended for stuffing data into other places.
-
You can not set a default link type. The reason is that it is not something you should be defaulting. Most issues do not need to be linked to others via issue links (the highest number I've seen was a shade under 10% of issues having links, and that turned out to be a bodge made by a previous admin who didn't understand…
-
Welcome to the Atlassian Community! No. That function is provided by Scriptrunner for Jira on Server/DC, but we can not yet recreate it on Cloud because of the limitations of Cloud in what we can code for. We're working with Atlassian to enable it, amongst other functions.
-
It is the same underlying problem I'm afraid - your database is not in the same shape that your Jira is expecting. An upgrade will try to change the shape to the new version, but it looks like your upgrade can not do it. I would go back again, install the version of Jira you had before upgrade, point it to the database and…
-
You can use Automations to populate fields.
-
The burndown is always based on the last column, and the last column only. The status category and resolution are utterly irrelevant. An issue is only "done" for the team if it is in the last column on their board.
-
So not a section, you want the version description. You can get this with a "get version" call - see https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-get
-
You need to look at the REST API to do this (springboot is not relevant, Java can make REST calls).
-
Welcome to the Atlassian Community! This usually tells us that your workflow is not set up to set a resolution on the issue when you close it. Your workflow should set a resolution either with a post-function or popping a screen that has resolution on it when moving to a status that you consider to be done, and clear it…
-
By default, sprint estimates will not show on sub-tasks issue types, because sub-tasks are not sprint items, and hence should not be estimated. How have you "added story points to fields"?
-
Welcome to the Atlassian Community! The best way to do this is not have a separate redundant field for a key. Why do you think you need a redundant and less useful field than the issue key? (I know this is a grumpy-looking post, but it really is about looking at your process and data integrity. Unless you have a legacy…
-
This suggests that your key is invalid, or not recognised because you have not added it to Bitbucket.
-
Welcome to the Atlassian Community! This suggests that you are using the wrong credentials in VS. What is the detail of the error VS gives you?
-
Welcome to the Atlassian Community! You need to talk to your admins, ask them why they have removed, or not granted you, access.
-
Hi, The requests are not stored, they are transient events - notifications go out, but nothing is stored, because there's no need to store it. The access request is "please may I have access to this", not a permission. You say "I've tried directly granting him access to the specific page, but without access to the entire…
-
Yep, all we can really tell you is "your workflow should match your desired process" Without knowing what your processes are, the only other thing I can recommend is to look very carefully at where you set and clear the resolution field. When a resolution is set, it means "this issue needs no more attention from humans".…
-
This is broadly what it says it is - you need to move to using a standard supportable file system NFS can work with older Windows file systems like NTFS and FAT, and all Unix file systems like ext1-4, btr and so-on, because these are all Unix compatible, and can be made to behave as though they are POSIX compliant.
-
Welcome to the Atlassian Community! This would be a spectacularly bad idea. Jira, including the apps and application you can add to it, including Assets (the current name for the old "Insight") cache and index their data outside the database. Also, most apps have database structures that are not intuitive for humans. TLDR:…
-
Welcome to the Atlassian Community! Trello is not a chat application. If you have configured it to talk to a chat application, then it is using whatever protocol that chat application uses.
-
Welcome to the Atlassian Community! Have you set your browser to spell-check in Czech?
-
Welcome to the Atlassian Community! We, the Community, mostly have no access to Atlassian systems, the best we can do is try to ask contacts within Atlassian about stuff (which is not something we want to do a lot), We have less information about your application than you do! To join one of the partner programmes, you need…
-
I agree, option 1 is nonsense, you end up with issues that are done and not done at the same time. Option 2 makes the most sense to me, but option 3 will not break anything (unlike 1)
-
Yes, that is what I would try next. The error message you have looks like a failure to read the database, which suggests it might not be updated by your upgrade correctly, so I would want to try the upgrade again, and read the logs for that as it runs.
-
Cloud is a lot further down the path of "no HTML injection" than Server/DC. You can not use it in message fields.
-
Welcome to the Atlassian Community! I am not sure what you mean by "parallel". Issues can always be worked on by many people, or even teams. A sub-task is a fragment of the parent issue, so Jira is saying the issue is logged at 20 weeks because that's what the work done on the parts of it add up to. Time logs and estimates…
-
Welcome to the Atlassian Community! The names of status and transition are set by the admin editing the workflow. You'll need to ask the other admins about this.
-
Um, yes, that document says all the issues must be marked as "done", which is "they are in the last column of the board"
-
Welcome to the Atlassian Community! Where are you struggling in my.atlassian.com? After you click on billing and then invoices of course.
-
Yes, that's why I asked. If the user directories are different (e.g. using Atlassian accounts for Cloud and Crowd for server), then there's no synchronisation possible, beyond duplicating and botching the accounts together (which will go wrong)
-
That is the notification settings for a team-managed project, not a notification scheme, but it is the right place to look. The important one is "you're the assignee for the issue" - that means you'll be mailed when the assignee is changed.