Different organisations use SCOPIDEA to track different kinds of Task ,bugs and defects. Depending on how your organisation is using SCOPIDEA, a Task could represent a software bug, a task, Issue etc.

User can add task in any project or able to add in any specific board 


Steps to Create Task:


1. Go to “Board” tab 


2. Click “Add Task” button.


3. Want to add more detail ,fill the “Create Task” form.


4. Click “Save” button.




The numbered fields shown in the screenshot are:


1. Projects — the 'parent' project to which the defect belongs.


2  Board -In Any project add task  Under some specific board 

3. Task Name — a unique name by which that defect is identified.


4. Task Detail — It comprises of four fields :-


  • Task Type — see below for a list of types.
  • Priority — the importance of the defect in relation to other defects. (See below for a list of priorities).
  • Sprint  sprint is the small components of any project or you can say module.


4.Watch by:- We need to type the user name to which we want to just show the defects.It is just like a CC in mail.


5. Tag — it is information attached to someone.


6. Due Date — the date by which this issue is scheduled to be completed..


7. Estimate Time (hrs) — the total amount of time required to resolve the issue, as estimated when the issue was created.


8. Spend Time (hrs) — the total amount of time taken by Assign to resolve the issue.


9. Progress — it shows the development on particular issue.


10. Description — a detailed description of the issue.


11. Browse file — to attach a file or screenshot to an issue.


12. Assign to — the person to whom the issue is currently assigned.


13. Task Flow — see below for a list of Flow. 




Some of the most important fields — 'Task Type', 'Priority' and 'Task Flow' — are described as follows:


Task Type


SCOPIDEA can be used to track many different types of Task. The default task types are listed below, but please note that your SCOPIDEA administrator may have customized this list to suit your organisation.


  • Bug — A problem which impairs or prevents the functions of the product.
  • Improvement — An enhancement to an existing feature.
  • New Feature — A new feature of the product.
  • Task — A task that needs to be done.
  • Custom Issue — A custom issue type, as defined by your organisation if required.





An issue's priority indicates its relative importance. The default priorities are listed below; note that both the priorities and their meanings can be customized by your SCOPIDEA administrator to suit your organisation.


  • Blocker — Highest priority. Indicates that this issue takes precedence over all others.
  • Critical — Indicates that this issue is causing a problem and requires urgent attention.
  • Major — Indicates that this issue has a significant impact.
  • Minor — Indicates that this issue has a relatively minor impact.
  • Trivial — Lowest priority.



Task Flow


Each issue has a Task flow, which indicates where the issue currently is in its life cycle ('workflow'). An issue starts as being 'Open', then generally progresses to 'Resolved' and then 'Closed'; or, depending on circumstances, it may progress to other statuses. Please also note that your SCOPIDEA administrator may have customized the available statuses to suit your organisation.


  • Open — This issue is in the initial 'Open' state, ready for the assign to start work on it.
  • In Progress — This issue is being actively worked on at the moment by the assign 
  • Resolved — A Resolution has been identified or implemented, and this issue is awaiting verification by the reporter. From here, defect are either 'Reopened' or are 'Closed'.
  • Reopened — This issue was once 'Resolved' or 'Closed', but is now being re-examined. (For example, an issue with a Resolution of 'Cannot Reproduce' is Reopened when more information becomes available and the issue becomes reproducible). From here, defect are either marked In Progress, Resolved or Closed. 
  • Closed — This issue is complete.