Comments
-
I was unsure because I saw “Jira Cloud Server”. now the image you show is from the main admin area. Can you look under any project and the project settings to see if you find Automation.
-
Ok. Your initial post seemed to imply a specific release. So you could check if the fix version was empty and no longer is... fixVersion was empty BEFORE startOfDay(-1d) and fixversion is not EMPTY Or (fixVersion changed or if you simply want to see where the FV changed... fixVersion changed after startOfDay(-1d)
-
Automation is built into Cloud but not for Server. You can purchase Automation for Jira app for server.
-
Something like this maybe fixVersion changed to 3.37 after startOfDay(-1d) Replace 3.37 with your version and adjust the time factor to suit.
-
You just need to deactivate their account if they no longer are in need.
-
If you can access the board settings you might add a quick filter to achieve your goals.
-
Hi Jim, I think the issue here is that you can only change the RT to one that is available within the current Issuetype for a given issue. example let’s say you have the following config: issuetype: RTs Incident: alarm, network outage Access: vpn, building, sharepoint Other: PC, phone, printer If the issue was opened using…
-
verify that your workflow support the transition from open to in progress. if so then you need to ensure you have permissions or that there isn't some rule/condition that prevents
-
any action (transition) based upon a comment cannot be associated w/in the workflow. This can only be done by some form of "listener" which is what an Automation trigger is. It listens for a comment on an issue and if it heard it triggers which leads to the Conditions and ultimately the action. So, in short a transition on…
-
What demo? Does your company own the http://banclyinc.atlassian.net/ instance? If not I don't see how you can access w/o being added as a user/customer. Confused.
-
Pocket change! :-D so do you actually have 10k users or is this some sort of odd bug happening here? Regardless I think you need to reach out to Atlassian Support and select Billing. I don't think anyone here can resolve this.
-
yes it should correct things. or you could simply start a new 'dummy' sprint and immediately close if you wanted. might make your reports a bit wonky.
-
were these issues in the right-most column when sprint completed. That is required to consider the issue as complete w/in the sprint.
-
Hi Lindsay, there are a number of ways to do this. Basically you want to place them into a "deep-backlog". You can do this by somehow tagging the issues you don't immediately care about and then use this "tag" to exclude those issues via the board's filter. Examples: * Priority - use maybe Lowest to represent those issues…
-
I recommend you reach out to Atlassian Support to see if they can assist you with this. If for any reason you can't open a support ticket try doing so under the "Billing" category.
-
can you share your actual workflow image or can you check to see if the (2) is in fact part of the status name by running a query.... status = "In Review (2)" when you begin to type the above into the JQL query box auto-complete will present available options. just trying to understand if that is part of the actual status…
-
Hi Leah, welcome to the Community. Disclaimer - I have not done this and only briefly played w/ difference between dates using Automation. Here is what I'm thinking.... * Trigger - date field changed * condition - issuetype = story or whatever are your types under the epic * condition - something to ensure you only execute…
-
may be a permissions issue. are you the site admin of this instance? Have you tried a different browser just in case? Have you logged out and back in?
-
not sure what you mean by "mail" group. In any event the RPs need to be individual Customer emails not some group/distro
-
maybe this is what you are trying to do? migrating-from-one-cloud-instance-to-another-cloud-instance
-
first things first - shutdown access to Instance A. It can get messy depending on what changed. I am assuming you are going to use CSV import here. First the easy part. You will want to run a query to find all issues in instance A that were created after your import to instance B. So you need to know exactly when you did…
-
Correct. Portal only users are Customers and not licensed. They will show under User management > JSM.
-
You enable at the board level. Go to board settings and at the bottom you will see Beta Roadmaps.
-
Go to the admin area and click on User management. In the Users screen select JSM as the product and you should see the list of users with JSM license. I suspect you have the default set to give new users JSM access which you should disable. You will need to edit all JSM users and deactivate those you don’t want/need to…
-
yep i keep that disabled personally as it creates unnecessary spam.
-
Hi Chris, welcome to the Community and JSM. So i'm not sure exactly what you have in mind around automating the process. You can elect to set up the project so that anyone in your domain will get added when they send an email. All of this is done within the Project's Customer Permissions with the exception of domain…
-
Hi Wilfried, I did a quick search in JAC for open suggestions and here is one - JSDSERVER-1733 . There seemed to be others worth searching out. With that said given the EOL plans around server I would question whether this would get implemented for Server. Maybe it will for Datacenter?
-
ah ok. so this is in fact associated w/ Zephyr. I don't use so can't really assist unfortunately.
-
I also recommend using a different issuetype as well. Regarding the use of automation. Automation is an "after-the-fact" action whereas the requirement it seems is pre-action, i.e. prevent transition. Now you could use automation to reverse the transition after it happened though a bit kludgy. Finally, here is an old post…
-
I have not experienced this can you please provide details, example, screenshots, etc. It might be a bug that needs to be reported but before we go there lets troubleshoot.